Hi Jon,
I changed alarms a bit after thinking about your problem. First off, repeated
alarms that throw an exception get stopped now. If you prefer to handle the
exception inside the alarm it will of course get rescheduled; only uncatched
exceptions cause a repeated alarm to get cancelled. S
Stefan Scholl wrote:
> Chris Double wrote:
>> On Mon, Nov 23, 2009 at 11:09 PM, Stefan Scholl wrote:
>>> Just the speed concerns me a bit.
>>
>> webapps.calculator uses the sqlite database backend which is quite
>> slow (sqlite isn't slow but for some reason using it as the web
>> database for
Hi everyone,
I have a question about threaded-servers: I need to send an object's
state to a connected client every 100 milliseconds. I'm using alarms
to do it and I'm having trouble canceling it once the client
disconnected. I subclassed threaded-server, and I've overridden
handle-client* so that
Chris Double wrote:
> On Mon, Nov 23, 2009 at 11:09 PM, Stefan Scholl wrote:
>> Just the speed concerns me a bit.
>
> webapps.calculator uses the sqlite database backend which is quite
> slow (sqlite isn't slow but for some reason using it as the web
> database for Factor it is). Try either chan
On Mon, Nov 23, 2009 at 11:09 PM, Stefan Scholl wrote:
> Just the speed concerns me a bit.
webapps.calculator uses the sqlite database backend which is quite
slow (sqlite isn't slow but for some reason using it as the web
database for Factor it is). Try either changing this to one of the
other ba
Just the speed concerns me a bit. I'm not the next Google,
Facebook, or Twitter. But a very unscientifically made benchmark
gives me very bad figures.
webapps.calculator emits a HTML page with 576 bytes. It uses
Furnace and Chloe.
Concurrency Level: 10
Time taken for tests: 29.187 seconds
