Sponsored Content
Full Discussion: What is a CPU with 2C/4T?
Special Forums Hardware What is a CPU with 2C/4T? Post 302462892 by chebarbudo on Friday 15th of October 2010 09:03:16 AM
Old 10-15-2010
Thanks scottn for your fast answer.
Is there an important efficency difference between 4 cores and 2 cores running 4 tasks?
 

10 More Discussions You Might Find Interesting

1. Solaris

How to down a particular CPU in a server, witch is having 16 CPU's

Hi.., my dout is a solaris server is having 16 cpu's. in tht one cpu running some error process, accupaying more space. I wanna down tht particular CPU only with out interrupting the other 15 CPU's. how can i do this. is there any command for this ?? (5 Replies)
Discussion started by: b.janardhanguru
5 Replies

2. UNIX for Dummies Questions & Answers

how to get persistant cpu utilization values per process per cpu in linux (! top,ps)

hi, i want to know cpu utilizatiion per process per cpu..for single processor also if multicore in linux ..to use these values in shell script to kill processes exceeding cpu utilization.ps (pcpu) command does not give exact values..top does not give persistant values..psstat,vmstat..does njot... (3 Replies)
Discussion started by: pankajd
3 Replies

3. Solaris

Multi CPU Solaris system shows 100% CPU usage.

Hello Friends, On one of my Solaris 10 box, CPU usage shows 100% using "sar", "vmstat". However, it has 4 CPUs and prstat and glance are not showing enough processes to justify high CPU utilization. ========================================================================= $ prstat -a ... (4 Replies)
Discussion started by: mahive
4 Replies

4. Solaris

cpu-shares vs cpu-cap in solaris

Can anyone tell me difference between cpu-shares vs cpu-cap in solaris & how FSS will work with cpu-caps ? (9 Replies)
Discussion started by: fugitive
9 Replies

5. Solaris

CPU and CPU-Utilization

Hi, I am a weblogic Admin I our env there are 5 servers running in one Solaris 10 Sparc machine. But when i tried for process status using <top> command I got the following output load averages: 1.75, 2.18, 2.12; up 134+08:28:49 22:24:21 79 processes: 77 sleeping, 1 running,... (1 Reply)
Discussion started by: Joseph Antoine
1 Replies

6. Solaris

Difference between CPU CHIP and CPU ID

Hi All, What is the difference between CPU CHIP and CUP ID on SUN/ Oracle M5000 servers.. Thanks in advance (3 Replies)
Discussion started by: kumarmani
3 Replies

7. UNIX for Dummies Questions & Answers

Is it possible to combine multiple CPU to act as a single CPU on the same server?

We have a single threaded application which is restricted by CPU usage even though there are multiple CPUs on the server, hence leading to significant performance issues. Is it possible to merge / combine multiple CPUs at OS level so it appear as a single CPU for the application? (6 Replies)
Discussion started by: Dissa
6 Replies

8. AIX

Entitled CPU lesser Than Used CPU !!

Hi All, It may be a n00b question, but i really want to know , How Entitled Capacity is less and Used CPU is more when there is no Free CPU is available in the managed system. I have 5LPARs in a MS with Dual VIO. Managed System CPU details Available: 0.20 Assigned to partitions: 15.80... (11 Replies)
Discussion started by: Thala
11 Replies

9. Red Hat

Esxi INTEL cpu vs esxi AMD cpu

Hi i have 2 esxi. one is amd based cpu and the other is intel based cpu. i have a redhat linux machine that was created in amd cpu esxi, now i need to migrate it (powered off) to INTEL based esxi. will the redhat machine will be OK with that? Thanks (2 Replies)
Discussion started by: guy3145
2 Replies

10. UNIX for Beginners Questions & Answers

Why Entitlement CPU can't be set to same as Virtual CPU?

I read that Entitlement CPU should be set to max 75% compare to Virtual CPU. May I know the reason. I have set the Entitlement CPU = Virtual CPU on AIX . It works fine . Can you help to understand. (1 Reply)
Discussion started by: gabhanes
1 Replies
yade-batch(1)						      General Commands Manual						     yade-batch(1)

NAME
yade-batch - batch system for computational platform Yade SYNOPSIS
yade-batch [options] [ TABLE [SIMULATION.py] | SIMULATION.py[/nCores] [...] ] DESCRIPTION
yade-batch Manage batches of computation jobs for the Yade platform; batches are described using text-file tables with parameters which are passed to individual runs of yade. Jobs are being run with pre-defined number of computational cores as soon as the required number of cores is available. Logs of all computations are stored in files and the batch progress can be watched online at (usually) http://local- host:9080. Unless overridden, the executable yade is used to run jobs. OPTIONS
--help, -h show this help message and exit --jobs=NUM, -j NUM Maximum number of simultaneous threads to run (default: number of cores, further limited by OMP_NUM_THREADS if set by the environ- ment: 4) --job-threads=NUM Default number of threads for one job; can be overridden by per-job with !THREADS (or !OMP_NUM_THREADS) column. Defaults to 1. --force-threads Force jobs to not use more cores than the maximum (see -j), even if !THREADS colums specifies more. --log=FORMAT Format of job log files: must contain a $, % or @, which will be replaced by script name, line number or by description column respectively (default: $.@.log) --global-log=FILE Filename where to redirect output of yade-batch itself (as opposed to --log); if not specified (default), stdout/stderr are used --lines=LIST, -l LIST Lines of TABLE to use, in the format 2,3-5,8,11-13 (default: all available lines in TABLE) --nice=NICE Nice value of spawned jobs (default: 10) --cpu-affinity Bind each job to specific CPU cores; cores are assigned in a quasi-random order, depending on availability at the moment the jobs is started. Each job can override this setting by setting AFFINE column. --executable=FILE Name of the program to run (default: /tmp/buildd/yade-0.80.1/debian/inst/bin/yade). Jobs can override with !EXEC column. --rebuild Run executable(s) with --rebuild prior to running any jobs. --debug Run the executable with --debug. Can be overriddenn per-job with !DEBUG column. --gnuplot=FILE Gnuplot file where gnuplot from all jobs should be put together --dry-run Do not actually run (useful for getting gnuplot only, for instance) --http-wait Do not quit if still serving overview over http repeatedly --generate-manpage=FILE Generate man page documenting this program and exit --plot-update=TIME Interval (in seconds) at which job plots will be updated even if not requested via HTTP. Non-positive values will make the plots not being updated and saved unless requested via HTTP (see --plot-timeout for controlling maximum age of those). Plots are saved at exit under the same name as the log file, with the .log extension removed. (default: 120 seconds) --plot-timeout=TIME Maximum age (in seconds) of plots served over HTTP; they will be updated if they are older. (default: 30 seconds) --refresh=TIME Refresh rate of automatically reloaded web pages (summary, logs, ...). --timing=COUNT Repeat each job COUNT times, and output a simple table with average/variance/minimum/maximum job duration; used for measuring how various parameters affect execution time. Jobs can override the global value with the !COUNT column. --timing-output=FILE With --timing, save measured durations to FILE, instead of writing to standard output. --randomize Randomize job order (within constraints given by assigned cores). SEE ALSO
yade (1) https://yade-dem.org/sphinx/user.html#batch-queuing-and-execution-yade-batch COPYRIGHT
(C) 2003--2012 Yade Developers Team This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA. BUGS
Please report bugs to the project's bug tracker at http://bugs.launchpad.net/yade AUTHOR
Yade Developers Team (http://www.launchpad.net/~yade-dev) yade-batch 2012-7-4 yade-batch(1)
All times are GMT -4. The time now is 08:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy