64bit windows vs 32bit windows and memory use
Posted: Sun Aug 17, 2014 7:20 pm
Quick question.
Having standalone (or vst as well?) app made by Flowstone, 32bit app that loads wave files.
From what I see, loaded waves - reserve memory equivalent of 32bit resolution. The question is not about it.
On 32bit operating system, when wave is being loaded - memory usage increases from zero to destination point.
But I noticed something on 64bit operating system. When wave is being loaded - task manager shows a memory usage spike that is 2x higher than the destination size, as if 64bit equivalent was reserved for a moment. Is this true, or this spike is not real?
Context:
This may cause a problem when loading large/long audio files. Because while having more GB on board - if the spike is real, then only half of available memory will be used (so having 4GB will make as if there was only GB). Because if the spike exceeds available size, then app will tell, that "there is no available memory". Do I understand it correctly? or just this spike will be unnoticed, because ut's some sort of native Windows operation?
Having standalone (or vst as well?) app made by Flowstone, 32bit app that loads wave files.
From what I see, loaded waves - reserve memory equivalent of 32bit resolution. The question is not about it.
On 32bit operating system, when wave is being loaded - memory usage increases from zero to destination point.
But I noticed something on 64bit operating system. When wave is being loaded - task manager shows a memory usage spike that is 2x higher than the destination size, as if 64bit equivalent was reserved for a moment. Is this true, or this spike is not real?
Context:
This may cause a problem when loading large/long audio files. Because while having more GB on board - if the spike is real, then only half of available memory will be used (so having 4GB will make as if there was only GB). Because if the spike exceeds available size, then app will tell, that "there is no available memory". Do I understand it correctly? or just this spike will be unnoticed, because ut's some sort of native Windows operation?