You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-user@db.apache.org by Manjula G Kutty <ma...@gmail.com> on 2006/03/10 22:39:32 UTC
Howmany concurrent users are supported by network server
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.
Thanks
Manjula
Re: Howmany concurrent users are supported by network server
Posted by Rajesh Kartha <ka...@gmail.com>.
Using Derby 10.1.2.1 - (330608) one of the my test ran with 140 clients.
These clients did a mix of I/U/D and Selects on a single table and atleast
50% ( 70) of these are concurrent at any given instant.
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 <ma...@gmail.com> wrote:
>
> Knut Anders Hatlen wrote:
>
> >Manjula G Kutty <ma...@gmail.com> 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
>
Re: Howmany concurrent users are supported by network server
Posted by Knut Anders Hatlen <Kn...@Sun.COM>.
Manjula G Kutty <ma...@gmail.com> writes:
> Knut Anders Hatlen wrote:
>
>>Manjula G Kutty <ma...@gmail.com> 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.
It's not possible to give an exact answer, since it depends on what
you consider acceptable, the type of load, the size and layout of your
tables, etc. However, to give an indication, I ran a test with up to
1000 concurrent connections. The attached graph shows the throughput
and average response time for an increasing number of connections.
The test clients operated on a 10 MB table (100 000 rows, 100 bytes
each). Each client executed one single-record operation (accessed by
primary key) per trasaction, of which 10% were insert operations, 10%
delete, 50% select and 30% update operations. The network server was
configured with 64 MB page cache, log and data were stored on separate
disks. Hardware configuration: 2x2.4GHz CPU, 2 GB RAM, 2 SCSI disks
(7200 rpm), disk write cache disabled. OS/JVM: Solaris 10 x86/Sun JVM
1.5.0. Derby version used was 10.2 (trunk).
The average response time for this mix of transactions is half a
second at 600 concurrent connections, one second at 850 clients and
1.5 seconds at about 950 clients. Maximum throughput is achieved at
about 150 connections.
Other configurations/workloads might give completely different
results, so YMMV.
--
Knut Anders
Re: Howmany concurrent users are supported by network server
Posted by Manjula G Kutty <ma...@gmail.com>.
Knut Anders Hatlen wrote:
>Manjula G Kutty <ma...@gmail.com> 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
Re: Howmany concurrent users are supported by network server
Posted by Knut Anders Hatlen <Kn...@Sun.COM>.
Manjula G Kutty <ma...@gmail.com> 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?
--
Knut Anders