Verge3 Memory Usage...
Displaying 1-9 of 9 total.
1
Omni
|
According to Windows Task Manager:
Verge memory size with some VC files, and an empty while loop
5,570 K
Verge memory size with some VC files, empty while loop, and a 1.10 meg JPG file loaded
9,980 K
Why the big difference? How does loading a one meg picture take four megs RAM?
EDIT: Maybe this is because of JPG image compression? The 24-bit uncompressed BMP comes out to 3.2 megs.
Posted on 2004-10-18 20:22:07 (last edited on 2004-10-18 20:23:57)
|
zonker6666
|
That would make sense --- once you load the jpg and put it in an image buffer its no longer compressed
Posted on 2004-10-18 21:10:48
|
Omni
|
In this case, however, I do think the difference between 4.5 megs taken for a 3.2 meg picture is significant. What's the other 0.7 meg going to?
Posted on 2004-10-18 21:58:29 (last edited on 2004-10-18 21:58:46)
|
Zip
|
Is it otherwise completely identical? Remember screen is a variably sized image too, and I'm sure there are lots of other 'hidden costs' for stuff. I must say, I've never had a problem with verge memomry usage, but it is quite resource hoggy.
Zip
[Edit: and images are stored in memory at 32 bit not 24, that's probably the extra]
Posted on 2004-10-18 22:50:24 (last edited on 2004-10-18 22:51:07)
|
zonker6666
|
I think a good way to find out is to set verge.cfg to verbose and read the log - it should tell where the memory's going
Posted on 2004-10-18 22:53:53
|
vecna
|
assuming your running in 32bpp bitdepth, all images are converted to 32bpp when theyre loaded = 4 bytes per pixel.
Posted on 2004-10-19 12:36:49
|
Interference22
|
After some discussion with Zip (who always likes a bit of optimisation) I tend to use my image files in funky ways, loading as few as possible but arranging them for maximum effect.
For instance, in my pet project, 'Perceptions,' all the dialogue boxes use a 64x64 graphic which I tile to the relevant size, using GrabRegion to paste it to screen where I want it. I'll have to post the code for this soon, it's really useful.
Still, memory shouldn't be much of a problem. Most people have at least 256mb RAM, right? there should only be a huge problem if you put a *crapload* of stuff into the memory.
Posted on 2004-10-19 12:45:18
|
Omni
|
This makes sense. Thanks, everybody.
Posted on 2004-10-19 18:54:09
|
vecna
|
Yeah out of all the various issues with V3, memory usage is like not even on my list. RAM is cheap folks. And VERGE isn't excessively memory-hogging compared to other things.
If you DO have memory problems, and images seem to be where msot of the memory is going, then running in 16bpp instead will chop your memory usage in half. It will be slightly uglier, but well, if you're running out of RAM on v3, you probably should be running in 16bpp!
Posted on 2004-10-19 22:34:36
|
