Version

menu_open

Choosing Worst Case Scenarios for Testing

Each memory pool may have a different worst case scenario. For example, playing sixty-four sounds at once greatly increases usage of the lower engine pool while only slightly increasing usage of the default memory pool. On the other hand, loading twenty banks all at once increases default engine memory usage without affecting lower memory pool usage. Therefore, we recommend that you don't use just one worst case scenario for all your tests, because you are likely to have many diverse situations in your game that will most likely use memory differently.

One particular situation to test occurs when SoundBanks are loaded and unloaded between levels, because this causes a peak in memory usage in the default memory pool. For example, when switching between Level 1 and Level 2 in your game, you may experience a peak in memory usage because there may be a brief period when both SoundBanks are loaded in memory.

[Caution] Caution

When performing tests to check peak memory usage for the Windows platform, you must ensure that the speaker setup configuration of the PC running the game is set to 5.1 or better. This is necessary because the sound engine performs some optimizations when the speaker setup is stereo and, therefore, may use less memory than in 5.1.


Was this page helpful?

Need Support?

Questions? Problems? Need more info? Contact us, and we can help!

Visit our Support page

Tell us about your project. We're here to help.

Register your project and we'll help you get started with no strings attached!

Get started with Wwise