Sponsored Content
Full Discussion: Sizing p7 systems
Operating Systems AIX Sizing p7 systems Post 302469118 by DGPickett on Thursday 4th of November 2010 07:36:39 PM
Old 11-04-2010
Neat! Remember that for the same total nominal spec-int or whatever, fewer processors is really faster. You only get full speed from the first, and then for each additional one sharing the same RAM, bus's, L2cache, L1cache, you get less. 4 cores of 20 > 8 cores of 10.
 

7 More Discussions You Might Find Interesting

1. Gentoo

Properly Sizing an x86 Server for Internet DNS?

Where I work, we have to very old Alpha boxes running OpenVMS 7. They also have Multinet and are using the BIND component for DNS services. We are planning on retiring those boxes and replacing them with x86 servers running Linux. I've decided to go with Gentoo Linux for this and I've inherited... (3 Replies)
Discussion started by: deckard
3 Replies

2. AIX

Sizing Mouse Pointer

On AIX machines 4.3, 5.1, 5.2 and 5.3 am having trouble seeing the mouse pointer in CDE. Found this on web To change the cursor to a large red X, run the following command . #xsetroot -cursor_name X-cursor -bg red Could someone kindly give me the command line wording to undo the above... (2 Replies)
Discussion started by: farl
2 Replies

3. Shell Programming and Scripting

Kinda a noob: Automatic window sizing and placement

I am attempting to create a script that runs automatically upon logging in and opens and places windows in appropriate places. I have the script running such that it starts during login, but I cannot get things how and where I want them. This should be relatively simple, I just can't figure it out... (7 Replies)
Discussion started by: wydileie
7 Replies

4. Linux

System sizing for X sessions

Hello all. I've been tasked with building a system that will have up to 50 concurrent users connected and using an X session running firefox. Is there some kind of standard sizing model available that will tell me what kind of network/CPU utilization I will be looking at? Or even better some... (1 Reply)
Discussion started by: ZekesGarage
1 Replies

5. Solaris

Sun hardware sizing

Hi, Never worked with Sun, but I have been presented to make a decision about Sun server hardware, since the application which we'll be running is not so popular and you guys might not have idea, for reference I can tell you our competitor is running same application (business volume 10 times... (1 Reply)
Discussion started by: tayyabq8
1 Replies

6. What is on Your Mind?

From Systems Admin to Systems Eng.

I have been wondering how do Systems Administrators do the jump into Systems Engineering? Is it only a matter of time and experience or could I actually help myself get there? Opinions? Books I could read? Thanks a lot for your help! (0 Replies)
Discussion started by: svalenciatech
0 Replies

7. UNIX for Dummies Questions & Answers

Using symbolic link for database MySQL in CentOS, not update sizing

I have no idea what I should set the topic here ==' This is my story, please you there kindly help me I'm quite newbie for this. ================================== My host server is CentOS, I spared 9.9GB for /var path that used by MySQL and...It's full because of heavy load traffic, then... (1 Reply)
Discussion started by: Kapom
1 Replies
iv_task(3)						    ivykis programmer's manual							iv_task(3)

NAME
iv_task_register, iv_task_unregister, iv_task_registered - deal with ivykis tasks SYNOPSIS
#include <iv.h> struct iv_task { void *cookie; void (*handler)(void *); }; void IV_TASK_INIT(struct iv_task *task); void iv_task_register(struct iv_task *task); void iv_task_unregister(struct iv_task *task); int iv_task_registered(struct iv_task *task); DESCRIPTION
The functions iv_task_register and iv_task_unregister register, respectively unregister, a task with the current thread's ivykis event loop. iv_task_registered on a task returns true if that task is currently registered with ivykis. A task is like a timer, but with an immediate timeout. When a task is registered, unless it is unregistered again first, the callback function specified by ->handler is guaranteed to be called once, in the thread that the task was registered in, some time after control returns to the ivykis main loop but before ivykis will sleep for more events, with ->cookie as its first and sole argument. When this hap- pens, the task is transparently unregistered. Tasks are mainly used for scheduling code for execution where it is not appropriate to directly run that code in the calling context (for example, because the current context might be run as a callback function where the caller expects certain conditions to remain invariant after the callback completes). The application is allowed to change the ->cookie and ->handler members at any time. A given struct iv_task can only be registered in one thread at a time, and a task can only be unregistered in the thread that it was regis- tered from. There is no limit on the number of tasks registered at once. See iv_examples(3) for programming examples. SEE ALSO
ivykis(3), iv_examples(3) ivykis 2010-08-15 iv_task(3)
All times are GMT -4. The time now is 05:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy