AnotherFoxGuy/polyvox
1
0
Fork 0
Code Issues Pull Requests Activity

The idea of a 'setTargetMemoryLimitInBytes' function was not really working out. It was too comp-lex and not really clear what the ideal size would be. I think user code needs to call setMaxNumberOfBlocksInMemory() and setMaxNumberOfUncompressedBlocks() directly, if they see from profiling toat too much camressing or paging is taking place.

Browse Source
This commit is contained in:
David Williams
2013-07-23 13:15:01 +02:00
parent 7cd115b33d
commit 7146b5ecdb
4 changed files with 22 additions and 66 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
tests/testvolume.cpp
View File

@ -281,9 +281,8 @@ TestVolume::TestVolume()
m_pSimpleVolume = new SimpleVolume<int32_t>(region);
m_pLargeVolume = new LargeVolume<int32_t>(region, m_pCompressor, m_pFilePager, 32);
//m_pLargeVolume->setMaxNumberOfBlocksInMemory(32);
//m_pLargeVolume->setMaxNumberOfUncompressedBlocks(16);
m_pLargeVolume->setTargetMemoryLimitInBytes(4 * 1024 * 1024);
m_pLargeVolume->setMaxNumberOfBlocksInMemory(32);
m_pLargeVolume->setMaxNumberOfUncompressedBlocks(16);
//Fill the volume with some data
for(int z = region.getLowerZ(); z <= region.getUpperZ(); z++)