Re^2: How to hobble a CPU

The test is a mix of both raw CPU power and I/O.
The workstation is receiving a lot of records (5000+) thru the LAN and needs to add them to a cockpit. The cockpit is refreshed after each received record.
The deployed workstations are about 50% less powerful (CPU, RAM) than my workstation and they can't refresh the cockpit quickly enough while mine can.

Regards,
Solostian

-- "Fortunately, ridicule does not kill..."

Comment on Re^2: How to hobble a CPU

Replies are listed 'Best First'.
Re^3: How to hobble a CPU by eric256 (Parson) on Jun 07, 2006 at 22:41 UTC
/me cringes at this idea. I'm assuming you have a reason for refreshing constantly...but is it a realy realy good reason? I mean wouldn't refreshing after batches work better for both stations with probably limited impact on the actual use? It is hard to tell, but realy if you want the performance of your target machine then test it on your target machine, thats the only way you are going to know how well it will run on the target machine. Best of luck ___________ Eric Hodges	[reply]

Replies are listed 'Best First'.

Re^3: How to hobble a CPU
by eric256 (Parson) on Jun 07, 2006 at 22:41 UTC

/me cringes at this idea.

I'm assuming you have a reason for refreshing constantly...but is it a realy realy good reason? I mean wouldn't refreshing after batches work better for both stations with probably limited impact on the actual use? It is hard to tell, but realy if you want the performance of your target machine then test it on your target machine, thats the only way you are going to know how well it will run on the target machine.

Best of luck

___________
Eric Hodges

[reply]