On Nov 11, 2011, at 1:23 PM, Steve Alex wrote:
> Hash is a library I wrote (beta) to speed up serializing and unserializing
> nested Active4D collections. I had used ObjectTools, but though I'd try
> another approach using a YAML like format. I got almost a four fold speed
> improvement. (probably the ObjectTools parser used - but used almost
> identical drivers?)
As the umpires say:
After further review, ...
Starting with 4D 2004, A4D 4.5. OT 2.1, I took a 42K OT blob and parsed it with
library method into a collection. I then serialized and unserialized the
collection using the Hash library.
I knew 4D 2004 seemed to run a little slower on an Intel Mac, but
4D On a 10.6 Macbook Air standalone:
Milliseconds to process blog with ot -> 7916
Milliseconds to process blog with hash -> 3024
4D On a PPC development server (I think compiled)
Milliseconds to process blog with ot -> 961
Milliseconds to process blog with hash -> 1005
I think I made some bad assumptions. Moving a 2004 DB to Intel may not be a
wise move. Seems that some stuff can be 3 to 7 times slower. Then there is the
compiled issue, but Active4D (and plugins) only stuff always seemed to be about
the same compiled on not.
I'll have to wait and see how the times come out on their Intel production
server - still may have some bad assumptions (rosetta).
Steve
_______________________________________________
Active4D-dev mailing list
[email protected]
http://list.aparajitaworld.com/listinfo/active4d-dev
Archives: http://vasudev.aparajitaworld.com/archive/active4d-dev/
