Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[storm] Find out why global memory allocations start taking much longer after a while #151

Open
perlun opened this issue Jul 7, 2019 · 2 comments
Labels

Comments

@perlun
Copy link
Contributor

perlun commented Jul 7, 2019

By adding #150, I came to the conclusion that memory_allocate seems to have some peculiarities going on, which sometimes degrades its performance by a factor of 500 to 1000 - i.e. the system goes from having reasonable real-time performance (making it possible to play mod files with #145) to being completely sluggish and barely usable.

This screenshot illustrates the problem ("Last memory allocation took" is the key):

image

I believe the only reasonable way to solve this is by fixing #4 using the approach suggested in #4 (comment) and I will see if it can be done with a reasonable effort.

@perlun perlun changed the title [storm] Find out why memory allocations start taking much longer after a while [storm] Find out why global memory allocations start taking much longer after a while Jul 8, 2019
@perlun
Copy link
Contributor Author

perlun commented Jul 8, 2019

Note: the screenshot is inverted because of a bug on my behalf; it's the global memory allocations that are taking an enormous amount of time, not the other way around.

@perlun perlun added the bug label Aug 6, 2019
@perlun
Copy link
Contributor Author

perlun commented Aug 6, 2019

Regarding the timings, I'm not sure how accurate they are. (We need better timers I think, especially ones that work in virtualized scenarios also. Perhaps using HPET or something would make sense; HPET in particular is blacklisted on Linux for some Intel chips though, so it might not be a great fit after all. 😒)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant