-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Performance issues #57
Comments
I am parsing the specified demo in 1.9 sec in my AOT compiled build, so you are probably doing something wrong. Are you maybe running it in Debug mode ? Also, could you run the Benchmark project and check the results. It should give you 1.5 sec as a mean time. |
Benchmark gave me 1.1 sec as mean time on my own demo i did some changes and switched to reading the bytes as async and adding them to the memory stream and running it in visual studio as release is down to 2.7 seconds if just build the exe and run it as release its 2.8 seconds current code:
|
Now you just need to build it using AOT compiler, and it should give you maxed out performance. There's also PR in progress which enables multi-threaded parsing ... |
Using multithreaded parsing I can read that demo in 1.9 secs on my Ryzen 7 3800X on an NVMe drive also. I believe for this workload at least .NET seems to run faster on ARM64 than x64 (the benchmark in the readme is on an Apple M1). I'll try to get the multithreaded parsing merged asap. |
The multithreaded parsing has now been merged and is available in v0.20.1 - thank you. |
Research
Description
Performance issues, in the Git you state that parsing a whole 1 hour demo can be done in 1.5 seconds.
i have a pc with 64 gigs of ddr5
AMD Ryzen 7 7800X3D
RTX 3070ti
running on a nvme drive.
but i am getting 8-10 seconds to just run this demo that ended 13-4. like 20 minutes of gameplay. Am i doing something wrong here? it seems rather slow.
Test was done on a console application on .net 8 with the below code.
Code to reproduce
Affected demos
https://drive.google.com/file/d/1Oi80oKMHf2DvIYSI42UL4kxvICLMGj2G/view?usp=sharing
The text was updated successfully, but these errors were encountered: