×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




It Depend... on how the app is written, how much memory, how many disk arms
etc etc etc.

I have a client with a 4core system with at least 32GB memory but only '10'
disk drives. Before I get shot, I didn't cfg or sell him that config. Unless
he pulls the files into memory ahead of time where possible, he gets I/O
Bound pretty quick.

Also consider IBM SMP LPP when running multiple cores...

On Tue, Jan 18, 2011 at 2:18 PM, <dieter.bender@xxxxxxxxxxxx> wrote:

... depends on your transactions and your hardware. For a 16 CPU iron 1- 2
million transactions should be no problem. To give a number: on a machine
with 16 CPUs 2 million transactions with 30 elementar operations each,
should be finished in 30 minutes, running in parallel without concurrent
workload.

D*B

--------------------------------------------------
From: "Vinay Gavankar" <vinaygav@xxxxxxxxx>
Sent: Tuesday, January 18, 2011 10:34 PM
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Subject: Database I/O throughput speeds

Hi,

Can any one give me some ball-park figures for number of I/O operations
(chain, update, write, delete) that can be achieved (per second or per
minute) in an RPG program running in batch mode (priority 50) on a high
end
newer model? I am not sure what model my company is going for, but it is
supposed to have 16 CPUs (if I heard it right). I realize that the
throughput may vary based on the other usage of the system, but I would
have
something to go by.

I am trying to gauge the impact of adding a few I/O operations to every
transaction when processing a batch of 1-2 million transactions. Our
development machine has nowhere near that power, so running a sample
program
on it would not tell me much.

Thanks
Vinay
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.