In praise of Fastmem

[Jane]

Related to NT, in that my experience involves an NT web server.

Capesoft's advertising for this product says "an alternative memory
allocator which is much faster than the default one for specific
situations."

I must have one of those situations.

I've built a service that ingests a fairly complicated clump of JSON from an
API.  This runs every 75 seconds.

As I watched the time for the ingestion, I found that the actual network
traffic takes about 10-15 seconds to receive the packet and then 45 to 70
seconds to parse the JSON and dump it into a memory table.

I'm using jFiles (because it has the correct initials!), but tried  cjson
with a bit slower results.

Then...  added Fastmem to my API ingester.  Whoosh.  The pics show it all.

Pretty cool improvement for 20 bucks, I'd say.

jf

[Bruce]

Thanks for the feedback Jane,

All glory goes to Dave Nichols who wrote it - we just publish it.

The biggest gain, by some distance, is in multi-threaded apps, where objects are being created and destroyed. Which coincidentally happens to be exactly what a NetTalk API Server (very multi-threaded) with jFiles (very much multiple objects) is.

So a NetTalk WebService API _really_ wins in this situation.

Cheers
Bruce

[Poul]

Is Fastmem  required for Clarion 11?
FastMem install does not know of C11

poul

[Bruce]

Hi Poul,

>> Is Fastmem  required for Clarion 11?

It's not "required" in any version of Clarion - Clarion works fine without it. But yes, it still has the same benefits in Clarion 11 (ie Clarion 11's memory allocator has not changed).

>> FastMem install does not know of C11

Thanks - I am aware of that. I have a version 2.0 which I am preparing for general release (just waiting for a support-gap to slip it into). In the meantime install the Clarion 10 version into your Clarion 11 folder.

cheers
Bruce