garbage collections, etc

new topic     » topic index » view thread      » older message » newer message

I'm back, with some more newbie questions!

I forget, but i think someone covered garbage collections already,, some,,
but is it possible, in a time-constrained section of code, to turn off all
garbage collection until that section of code is done? What about turning
off type checking and range/bounds checking in a proven section of code and
then turning those back on too? Can garbage collection be interrupted
between each var being collected, to be resumed later?

Also, i noticed occasionally when it seems like windoze has un-cached
something Eu needs, it takes on average .4 sec to get the Eu task back up to
speed if it's been idle, especially in disk accesses. That isn't bad,
really, on bigger apps, 2 sec is about average. But is there any way to tell
this uncooperative OS to remember i want Eu ready at my beck all the time?,
to cut that .4 sec lag down,, `cause it could add up, and i can see in the
future i may be faced with 10 sec of lag as windoze reloads the uncached Eu
sessions. I have 64Meg of ram, so i *shouldn't* <wince> have a problem,
right? <sigh>

Kat,
hoping to extract RawBlazingSpeed from BlahRaisingSpeed.

new topic     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu