Thank you for suggestion, Jeremy. Installing this gem had an interesting effect. Cost of one action execution in ruby-prof dropped significantly, from 40k to 20k of 'process time units'. Quick test showed that 'best case scenario' action processing time dropped from 7ms to 6ms. Stress tests showed relatively small improvement in throughput (31 to 33 for untuned ruby and 41 to 43 for gc-tuned ruby). Amount and total size of short lived objects stayed about the same, so did overall garbage collection time.
All in all, it is definitely worth it to use sequel_pg gem, but it did not affect short lived object's generation rate. On Dec 30, 12:55 pm, Jeremy Evans <[email protected]> wrote: > On Dec 29, 9:53 pm, Olek Poplavsky <[email protected]> wrote: > > > I am using postgres 8.4 ('pg' driver), > > Try installing the sequel_pg gem (which I wrote). It does the type > conversion in C. This is faster in general and also avoids creating a > lot of intermediate objects, which results in less GC churn. Sequel's > postgres adapter will automatically pick up sequel_pg if it is > installed and you are using the pg driver. Please give it a shot and > let me know how much of a speedup it gives you. > > Thanks, > Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-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/sequel-talk?hl=en.
