-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Keeny,
On 2/16/2009 5:15 AM, keenny wrote:
> I'm currently working on a system that must be able to serve thousands of
> requests per sec. The requests/responses contains only small amounts of data
> (ajax XMLHTTPRequests) and are not long lived (conn
Not in this case, but the requirements this poses on the back-end system is
similar. As explained above, the latency will be high, but so must the
throughput.
awarnier wrote:
>
> keenny wrote:
>> Hello all,
>>
>> I'm currently working on a system that must be able to serve thousands of
>> requ
awarnier wrote:
>
> keenny wrote:
>> Hello all,
>>
>> I'm currently working on a system that must be able to serve thousands of
>> requests per sec. The requests/responses contains only small amounts of
>> data
>> (ajax XMLHTTPRequests) and are not long lived (connection keep). I'm
>> using
>>
> From: keenny [mailto:kee...@start.no]
> I was just wondering if anybody has any opinions
> as to how this
> can be done most effectively (highest throughput, low cpu
> consumption etc).
> Some alternatives being:
>
> lighttpd -> mod_proxy -> tomcat -> application code
Lots of moving parts. Ther
keenny wrote:
Hello all,
I'm currently working on a system that must be able to serve thousands of
requests per sec. The requests/responses contains only small amounts of data
(ajax XMLHTTPRequests) and are not long lived (connection keep).
Whenever I see a description like the above, my imme
keenny wrote:
Hello all,
I'm currently working on a system that must be able to serve thousands of
requests per sec. The requests/responses contains only small amounts of data
(ajax XMLHTTPRequests) and are not long lived (connection keep). I'm using
java to generate the responses. Static conten
