Unix Programming - Re: Best Programming language for Network programming (complex server

This is Interesting: Free IT Magazines  
Home > Archive > Unix Programming > May 2007 > Re: Best Programming language for Network programming (complex server





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Re: Best Programming language for Network programming (complex server
B. Augestad

2007-05-24, 1:19 pm

anup.kalbalia@gmail.com wrote:
> On May 24, 10:13 pm, "B. Augestad" <b...@metasystems.no> wrote:
[vbcol=seagreen]
>
> 1. I would correct myself by replacing the term real-time by "having
> bounded response times". By real-time I meant that the server has to
> respond extremely quickly.


And what do you mean by "extremely quickly"? ;-)

> 2. There shall be both UDP and TCP packets sent to the client.


To the client or to the server? I assumed that the client sent the data
to the server, is that incorrect?

> But
> there is some data (like ticker data where guaranteed packet delivery
> is not essential) which does not require to be TCP as it can do away
> with the associated overhead.


Is there really much overhead to use TCP if you're going to use both TCP
and UDP anyway? (Assuming that the network isn't a bottleneck and
drops/retransmits)

> 3. Clients can be around 10000 or even more...scalability is a big
> issue. Data will be huge and shall be of the range of 20-50 Kbps
> during peak hours


So you'll have 10000 clients, each sending 50 kilobytes per second. (or
is that bits per second?) That's 488MB/s of data.

If you plan to shove that much data into an Oracle database, you have an
interesting project. Even assuming that you meant bits instead of bytes
and that you have a significant protocol overhead, you still have to
move dozens of MB/s.

Even if you can make the TCP/UDP server fast enough, the database server
and the IO subsystem will probably become a bottleneck.

Q: Any idea of the transaction sizes(KB) and the number of
transactions/second?
Q: Any thoughts on what hardware/os you plan to run this on?

> 4. UDP Data shall be generally binary data.


Can you accept packet loss?

> 5. Database can be Oracle/SQL. I am also keen on using some in memory
> database to improve performance. still tinkering with them. Any
> suggestion on that shall be helpful too.


Berkeley DB?
http://www.oracle.com/technology/pr...y-db/index.html

BTW, you probably want to read this asap: http://www.kegel.com/c10k.html

Bjørn

--
Looking for an embeddable web server?
http://www.metasystems.no/products/...nder/index.html
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com