You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to check if my tool (which analyzed damaged images) works correctly with any damaged images. And therefore in an unit-test I just try to sequentially "damage" every byte of an image and check if everything works as expected. But preliminary estimation showed that this experiment would require 94 hours on my laptop. And cpuprofile shows, that 96% of time is utlized in github.com/ulikunitz/xz/lzma.(*decoder).decompress. So I was wondering: is there a way to disable the decompression (or may be cache the results)?
Hello!
I'm trying to check if my tool (which analyzed damaged images) works correctly with any damaged images. And therefore in an unit-test I just try to sequentially "damage" every byte of an image and check if everything works as expected. But preliminary estimation showed that this experiment would require 94 hours on my laptop. And
cpuprofile
shows, that96%
of time is utlized ingithub.com/ulikunitz/xz/lzma.(*decoder).decompress
. So I was wondering: is there a way to disable the decompression (or may be cache the results)?When I just change (in
./pkg/uefi/section.go
):to
I receive a speed-up in 9.5 times.
Related: #311
Related: #302
The text was updated successfully, but these errors were encountered: