Hi,
I'm wondering what the performance impact of using beanstalk with
persistence switched on is.
My intuition (not based on reading the source so please correct me!)
is that the cost of turning on persistence will be to add some disk IO
to every operation. To get an initial idea I created a simple test to
call put 100,000 times against 1.3, 1.4 (persistence on and off). I
got the following results (tested on a MacBook running OS X with no
other disk IO):
Test beanstalk 1.3
user system total real
put 4.150000 1.730000 5.880000 ( 10.867630)
Test beanstalk 1.4 without persistence
user system total real
put 4.110000 1.720000 5.830000 ( 10.831340)
Test beanstalk 1.4 with persistence
user system total real
put 4.200000 1.720000 5.920000 ( 12.703707)
This seems to indicate that the cost in time is about 20%. I'd imagine
that this would be much higher on systems doing a lot of IO, but
didn't run any tests.
The test is here in case anyone wishes to extend it
<http://gist.github.com/202156>.
Finally, thanks for getting such a useful feature out of the door.
I've been looking forward to this for some time :)
Regards,
Martyn
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"beanstalk-talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/beanstalk-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
