Of course, I did not time the operations as I was more interested in any memory leaks over a long run.
FYI:
Finally the database ended up with:
Table with 29 million rows
----------------------------------------
ij> select count(*) from nstest.nstesttab;
1
-----------
29004516
1 row selected
39GB space used by the database
--------------------------------------------------
The disk usage shows:
swift SERVER/rc2> du -h nstestdb/
5.1M nstestdb/log
0 nstestdb/tmp
39G nstestdb/seg0
39G nstestdb/
(Again, this does not indicate the actual db size)
840K connections were made to the Server over the entire run:
-----------------------------------------------------------------------------------------
swift SERVER/rc2> tail -f derby.log
Connection number: 840555.
Connection number: 840556.
Connection number: 840557.
Connection number: 840558.
Connection number: 840559.
Connection number: 840560.
Connection number: 840561.
Connection number: 840562.
Connection number: 840563.
Connection number: 840564.
-Rajesh
On 3/10/06, Manjula G Kutty
<[EMAIL PROTECTED]> wrote:
Knut Anders Hatlen wrote:
>Manjula G Kutty <[EMAIL PROTECTED]> writes:
>
>
>
>>Hi,
>>
>>I would like to know an estimate of howmany concurrent users are
>>supported by derby network server. I know its hardware dependent, but
>>for instance assuming a Windows box w/ 2Gb memory, single CPU, single
>>7200rpm IDE drive.. Each user will be doing insert, delete, update and
>>select.
>>
>>
>
>What do you mean by supported? The number of concurrent connections
>you can have without running out of memory? The number of concurrent
>connection you can have with acceptable performance, for some
>definition of acceptable? Something else?
>
>
>
Hi
Thanks for taking time to look into my mail.
I would like to get the number of concurrent connections you can have
with acceptable performance.
Thanks,
Manjula
