[Seaside] speed of VM vs. speed of database
Boris Popov, DeepCove Labs
boris at deepcovelabs.com
Sun Dec 4 17:34:55 UTC 2011
The whole subject is like asking if a car goes faster with a trailer attached. Of course not, but it is often needed anyway.
On 2011-12-04, at 12:29, "Chris Muller" <asqueaker at gmail.com> wrote:
> Work done straight with the VM will be at least 100X faster compared
> to the "same" work done with a database. To "read" a collection in
> the VM (e.g., #do:), just a few bytecodes are executed. But to do
> that with objects in a database means it has to convert the objects in
> the database into Smalltalk objects first. This conversion requires
> the execution of thousands of additional bytecodes.
> But databases are still useful for the features they provide that
> images don't, such has having large models that exceed the size of
> memory, or letting multiple users access and update a model at the
> same time, or high-availability and consistency, etc.
> On Sat, Dec 3, 2011 at 11:56 AM, sergio_101 <sergiolist at village-buzz.com> wrote:
>> i am currently developing an app just for fun..
>> during my day job, i am a developer using a web framework that
>> directly connects to a database (mysql)..
>> one of the things we always do is craft our queries to use use the
>> database only for all queries and selections. when you use the
>> database for anything other than trivial queries, the difference is
>> the speed of the query is totally evident..
>> i am just wondering how the speed of the smalltalk VM compares to the
>> speed of pulling results from a database and shoving them into an
>> photographer, journalist, visionary
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside