Dani,

Thank you, for a very large value of "thank you." I woke up this morning
all excited to write some tests, and you had already done the work. It's
really great that you took the time to do the tests, to share your
conclusions and your test method. Thank you!

In my case, I'm not so kind or generous ;-) I've got a specific method that
I'm using for testing. I pass in a method and it does the work. This is a
fixed data set, so the results are always identical. The only thing I'm
changing is how I'm building up the block of text. I posted about the four
method I tired and they were all the same, about 6 minutes. I went back,
added a new test for *SET TEXT TO BLOB* in the loop and then one call to *BLOB
to text* at the end.

The results? What otherwise take about 6 minutes now takes just over 2
seconds. I had to run it a few times to convince myself I wasn't imagining
things. I wasn't. I thought that I was past the point where I'd ever see a
100x (well, x160 in this case) improvement from a small code change.

So thank you all for this information, it's a game-changer for me!

Onto the other point, memory. A Dani commented, if you need text then you
have to briefly double the RAM consumed. In my case, I need text. (The text
is passed to a plugin that doesn't accept BLOBs in this situation.) What do
people thing about RAM these days? I'm still kind of conservative. Tim
Nevels (off-line) said to me the other day, "David, why are you worrying
about memory? Everyone has tons of memory." I'm already not worrying about
performance in advance, and I *don't* feel like spending more time worrying
about security, so can't I worry about memory a bit? Where do you guys
stand on this on modern gear? When was the last time you bumped into
harmfull memory constraints?

Thanks
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to