Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Art S. Kagel — — source: Usenet: comp.databases.informix
eagle_jyjh@citiz.net wrote:
> Given an database, how can I get the throughput of informix ?
> such as how many query/update opertions per seconds informx can
> support?
> Because my application may submit serveral thousands of database
> operations per seconds,
> I want to calculate how many prcocess of my application can be started.
I'm joining the 'It depends!' bandwagon. I would just add that IDS tends to
scale very well especially on an SMP box. One test app we did was able to
perform 4000 inserts per second on a test server with one process inserting.
With 6 processes it averaged out at 20000 rows inserted/sec for the test
suite. This was an optimized dumb test app with maximum comm buffers sizing
and using PUT cursors and committing every 201 rows (application
requirement). Don't know where the ceiling of reasonable scaling would have
been, but that would be VERY environment dependent and YM will surely vary.
I know that the Real-Time Datablade is capable of inserting many times what
I could do in pure ESQL/C.
Art S. Kagel
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.