Late to the party

Shaggy — Wed, 02 Sep 2009 13:04:32 +0000

Late to the party again...

Benchmark it. Send 'ab' or 'seige' (or other flavours of the day) after each of your publicly accessible components with increasing numbers of simultanious connections and requests, and see how the io, cpu, etc. hold up.

It's the only way to get an even half-accurate estimate of what you'll be looking at before the faceless hoards come a-knockin'.

Cheers,
Shaggy.

JB, with reference to your

davecoventry — Wed, 26 Aug 2009 15:41:37 +0000

JB, with reference to your comment on how well the application is written, if you were writing an ajax client, what would you be on the lookout for in terms of minimising server load?

I'm thinking that the timing mechanism should be in the javascript so that the browser and the client machine can deal with it, but obviously the access to the database has to be handled on the server.

This depends so much on the

JeevesBond — Wed, 26 Aug 2009 13:16:12 +0000

This depends so much on the application and how well it's written!

You should create some automated chat scripts to simulate conversation, then see how much you can load the server before it gets into trouble.

Sorry if that wasn't the answer you were looking for, but if I were to try giving an arbitrary number I would just be pulling it out of my arse.

I would guess it would

davecoventry — Mon, 24 Aug 2009 12:59:45 +0000

I would guess it would depend on the frequency of calls to your database.

If you set it to poll the database every second, you are going to have problems a lot earlier than if you poll it every 10 seconds.

I know this is obvious, sorry.

Which ajax chat client are you using?

Anyone know at all??

the311guy — Mon, 24 Aug 2009 11:02:59 +0000

Anyone know at all??