Benchmark

, ,
1

Imported from previous forum

2

[ original email was from Le Floch mikael - mikael.lefloch@internet-quest.fr ]
Do you have any idea about the performance of Coppelia Fix Engine ?

ex : XX msg/sec max ?

Thank you

3

I wrote a very light weight fix engine that can send up to 5000 messages a second when the receiver is a program that only reads from a socket. With this test program, I’ve clocked Coppelia at 85 msgs/sec for a 10,000 message burst. I’m running a 2x700 MHz Penguin with 256MB RAM, LINUX 6.2.

> Do you have any idea about the performance of Coppelia Fix Engine ?
>
> ex : XX msg/sec max ?
>
>
>
> Thank you
>

4

[ original email was from Matt Koehler - matt.koehler@transacttools.net ]
> I wrote a very light weight fix engine that can send up to 5000 messages a second when the receiver is a program that only reads from a socket. With this test program, I’ve clocked Coppelia at 85 msgs/sec for a 10,000 message burst. I’m running a 2x700 MHz Penguin with 256MB RAM, LINUX 6.2.

Some benchmarks from a different FIX engine (CameronFIX) which i think might be slightly less expensive:

PIII 600Mhz Laptop (Win 2000, JDK1.3) - 700 per second

Sun 420R (450Mhz) (Solaris, JDK1.3) - 500 per second per CPU

Dual PIII 1000Mhz (Win 2000, JDK1.3) - 4000 per second

5

What kind of FIX message did you use to test? Were they routed to any service provider? I meant if they have been saved to a database by the FIX engine. The performance looks too great.

> > I wrote a very light weight fix engine that can send up to 5000 messages a second when the receiver is a program that only reads from a socket. With this test program, I’ve clocked Coppelia at 85 msgs/sec for a 10,000 message burst. I’m running a 2x700 MHz Penguin with 256MB RAM, LINUX 6.2.
>
> Some benchmarks from a different FIX engine (CameronFIX) which i think might be slightly less expensive:
>
> PIII 600Mhz Laptop (Win 2000, JDK1.3) - 700 per second
>
> Sun 420R (450Mhz) (Solaris, JDK1.3) - 500 per second per CPU
>
> Dual PIII 1000Mhz (Win 2000, JDK1.3) - 4000 per second
>
>

6

Yes. Agree.
Would you, who offered the benchmark kindly before, pls let us know more detail about that?
Just a short description of the process and What in it is ok.
Thank you very much.

Cindy

> What kind of FIX message did you use to test? Were they routed to any service provider? I meant if they have been saved to a database by the FIX engine. The performance looks too great.
>
> > > I wrote a very light weight fix engine that can send up to 5000 messages a second when the receiver is a program that only reads from a socket. With this test program, I’ve clocked Coppelia at 85 msgs/sec for a 10,000 message burst. I’m running a 2x700 MHz Penguin with 256MB RAM, LINUX 6.2.
> >
> > Some benchmarks from a different FIX engine (CameronFIX) which i think might be slightly less expensive:
> >
> > PIII 600Mhz Laptop (Win 2000, JDK1.3) - 700 per second
> >
> > Sun 420R (450Mhz) (Solaris, JDK1.3) - 500 per second per CPU
> >
> > Dual PIII 1000Mhz (Win 2000, JDK1.3) - 4000 per second
> >
> >
>