Comments on: Highly responsive ajax applications without excess requests and bandwidth waste?

By: Lindsey Stickel

Lindsey Stickel — Wed, 02 Jun 2010 01:39:12 +0000

hey,I discover that your website is very informative and helpful and we wonder if there can be a possibility of acquiring More web content like this on your blog. If you willing to support us out, we can be willing to compensate you… Best regards, Lindsey Stickel

By: georgi

georgi — Sat, 24 Jan 2009 08:40:26 +0000

@frank: if you have 10 000 concurrent users each second then you must have quite of a web server… In this situation you would need a database cluster ( a whole farm ) as your application is write-intensive. I don’t think you can cache anything as each user will be served by the web-server by a new instance of your script and you have no idea what other users are doing – one would think you can “cache” the data coming from all users in files on the hard drive and then run a script each X seconds which will write those files in the db but, hey – the DB is a file on the hard drive, too – you will be adding an additional layer which ( in my opinion ) will at least not make the process more efficient.
You can try using a DBE with transaction support ( most of them do have such support ) and maybe commit the transaction each X seconds.

By: frank

frank — Sat, 24 Jan 2009 08:15:21 +0000

This is an interesting subject. Are you still there? Didn’t see much followup. I was debating on developing a mechanism that would syncronize a client and server in the dependency caching way. In this way, the client must notify the server that there has been a new action that requires a CRUD routine and server in turn would adopt and post back the collection of changes the client had compiled while disconnected.

My question is, what do you do to address an application that must make requests to the server by the hundreds of thousands per minute. For example, an application with 10 thousand concurrent users, who’s browsers are all “short polling” the server, will make 600,000 http requests per minute. What kind of overhead would this create if making mini round trips to the database and is there an alternate approach so that collections or arrays can be used and manipulated on the server without having to batch their data in with SQL each second.