Sponsored Content
Full Discussion: High Performance Computing
Special Forums UNIX and Linux Applications High Performance Computing High Performance Computing Post 302257411 by humbletech99 on Wednesday 12th of November 2008 05:09:32 AM
Old 11-12-2008
1. CPU intensive computation of a single task
2. Parallel computation of a task broken down into pieces
3. Storage across many commodity nodes with scalability and i/o performance
4. The solutions do not need to be geographically dispersed, same server room is fine.
 

6 More Discussions You Might Find Interesting

1. AIX

Performance Problem - High CPU utilization

Hello everybody. I have a problem with my AIX 5.3. Recently my unix shows a high cpu utilization with sar or topas. I need to find what I have to do to solve this problem, in fact, I don't know what is my problem. I had the same problem with another AIX 5.3 running the same... (2 Replies)
Discussion started by: wilder.mellotto
2 Replies

2. High Performance Computing

IBM Scheduler for High Throughput Computing on IBM Blue Gene P

A lightweight scheduler that supports high-throughput computing (HTC) applications on Blue Gene/P. (NEW: 06/12/2008 in grid) More... (0 Replies)
Discussion started by: Linux Bot
0 Replies

3. High Performance Computing

What does high performance computing mean?

Sorry, I am not really from a computer science background. But from the subject of it, does it mean something like multi processor programming? distributed computing? like using erlang? Sound like it, which excite me. I just had a 3 day crash course in erlang and "Cocurrency oriented programming"... (7 Replies)
Discussion started by: linuxpenguin
7 Replies

4. High Performance Computing

High performance Linkpack

hello everyone , Im new to HPL. i wanted to know whether High performance linpack solves linear system of equations for single precision airthmatic on LINUX. it works for double precision , so is there any HPL version which is for single precision.\ thanks . (0 Replies)
Discussion started by: rahul_viz
0 Replies

5. Emergency UNIX and Linux Support

Performance investigation, very high runq-sz %runocc

I've just been handed a hot potato from a colleague who left :(... our client has been complaining about slow performance on one of our servers. I'm not very experienced in investigating performance issues so I hoping someone will be so kind to provide some guidance Here is an overview of the... (8 Replies)
Discussion started by: Solarius
8 Replies

6. High Performance Computing

High Performance Linpack Compiling Issue

I'm trying to compile Linpack on a Ubuntu cluster. I'm running MPI. I've modified the following values to fit my system TOPdir MPdir LAlib CC LINKER. When compiling I get the following error: (the error is at the end, the other errors in between are because I've ran the script several times so... (0 Replies)
Discussion started by: JPJPJPJP
0 Replies
ABRT-RETRACE-CLIEN(1)						    ABRT Manual 					     ABRT-RETRACE-CLIEN(1)

NAME
abrt-retrace-client - Handles the communication with Retrace server. SYNOPSIS
abrt-retrace-client <operation> [options] DESCRIPTION
This tool is able to communicate with Retrace server: create a new task, ask about task's status, download log or backtrace of a finished task. Integration with libreport events abrt-retrace-client can be used as an analyzer for application crashes which dump core. Example usage in report_event.conf: EVENT=analyze analyzer=CCpp abrt-retrace-client OPERATIONS
create Creates a new task. Prints task ID and password to stdout. Either -d or -c is required. status Prints task's status to stdout. Both -t and -p are required. log Prints finished task's log to stdout. Both -t and -p are required. backtrace Print finished task's backtrace to stdout. Both -t and -p are required. batch Runs all operations in one step: creates a new task, periodically asks for status (the period is specified by --status-delay option) and downloads the result when finished. If the task was successful backtrace file is saved, otherwise log is printed to stdout. Either -c or -d is required. OPTIONS
-v, --verbose be verbose -s, --syslog log to syslog -k, --insecure allow insecure connection to retrace server --url URL retrace server URL --headers (debug) show received HTTP headers -d, --dir DIR read data from ABRT problem directory -c, --core COREDUMP read data from coredump -l, --status-delay delay for polling operations (seconds) --no-unlink (debug) do not delete temporary archive created in /tmp -t, --task ID ID of the task on server -p, --password PWD password of the task on server AUTHORS
o ABRT team abrt 2.1.11 06/18/2014 ABRT-RETRACE-CLIEN(1)
All times are GMT -4. The time now is 11:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy