Re: How can I get throughput of informix such as how many query/update operations per second?
A poster asked how to measure Informix throughput (queries/updates per second). Respondents said no vendor or generic figure exists, since throughput depends on query complexity, number of tables/rows returned, CPU, memory, disk type and layout, database size and tuning. The advice was to simulate your own application and environment using performance/load testing tools such as LoadRunner or TestComplete. TPC benchmarks (e.g. TPC-C) were noted as valid only for the exact tested configuration and of limited comparative value. The thread ends in jokes about Yugos rather than a concrete measurement recipe.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
you probably need some performance testing tools such as LoadRunner or TestComplete
no vendor will say their database will give x queries per second. the number of queries/updates per second really depends on the complexity of each query. how many tables, how many rows they return amongst other factors hence the reason you really need to simulate your own environment to obtain those sorts fo figures for your application
scottishpoet wrote: > no vendor will say their database will give x queries per second. the > number of queries/updates per second really depends on the complexity > of each query. how many tables, how many rows they return amongst other > factors > > hence the reason you really need to simulate your own environment to > obtain those sorts fo figures for your application > What about TPC/? benchmarks :D Nah.
TBP does tell you what performance you get with specific transactions it has limited usefulness for comparason purposes Having worked on TPC performance testing and help write TPC-D....
scottishpoet wrote: > TBP does tell you what performance you get with specific transactions > > it has limited usefulness for comparason purposes > > Having worked on TPC performance testing and help write TPC-D.... oops ... TBP TPC TCP ... TCP does tell you what performance you get with specific transactions It will not tell you that you will get the same number of transactions in your environment with your application
>scottishpoet wrote: > > no vendor will say their database will give x queries per second. the > > number of queries/updates per second really depends on the complexity > > of each query. how many tables, how many rows they return amongst other > > factors > > > > hence the reason you really need to simulate your own environment to > > obtain those sorts fo figures for your application > > > >What about TPC/? benchmarks :D > >Nah. Your tpc/c benchmark will only be valid for the precise configuration. It is meant as an indication of a theoretical limit. Your Miliage May Vary. Without knowing CPU, amount of memory, types of disk, even the make/model of the motherboard can and will effect your performance. Layout on Disk, size of database and tuning of the database will affect your results. I'll throw out a number... 1 million transactions per second. Now if you can't do that, then you're not worthy of being a programmmer and you should go back to delivering pizzas in your suped up Yugo. On a more serious note, you can look at the financial foundataion components to get an idea of how many ticks per second could be loaded. ;-) _________________________________________________________________ Get FREE Web site and company branded e-mail from Microsoft Office Live http://clk.atdmt.com/MRT/go/mcrssaub0050001411mrt/direct/01/
> I'll throw out a number... 1 million transactions per second. Now if you > can't do that, then you're not worthy of being a programmmer and you > should go back to delivering pizzas in your suped up Yugo. Don't be so harsh to Yugo :o) Given its very modest hardware it performs very well. Even off the road (tested). And it almost does not need a mechanic. Sounds a little like Informix, doesn't it? :-)