Download and uncompression are slower than expected. about nist-data-mirror HOT 7 CLOSED

Got down to 44 seconds. Pull request at #116

from nist-data-mirror.

I am creating a pull request from my fork where I cannot create issues.. I was expecting to be able to create a properly named branch after creating this issue. Apparently this is not how it is done. I will submit a proper pull request in a few days.

from nist-data-mirror.

"master" as of now takes 50 minutes on my Windows 10 machine. Initial experiments with appropriate buffering gives a run time of 2-3 minutes.

from nist-data-mirror.

I noticed a performance issue too. Moving from one VM to another, the disk must be configured differently since running the mirror went from about 5 minutes to 45 minutes and seems to be mostly due to the lack of I/O buffering.

Thanks @trandersen-ufst for your PR. I came here to submit the same thing.

from nist-data-mirror.

@sellersj You're welcome. Now a month later we ended up not using this but instead saving the dataDirectory of a normal dependency-check:check run in a SNAPSHOT Maven artifact which can then be unpacked when needed for "almost-offline" usage in our CICD build server. As the download+update bit is then decoupled from the actual check, we expect this to be very robust.

from nist-data-mirror.

PR #116 merged so I think that this is resolved. I tested it with the 1.6.0 release and it was much faster.

from nist-data-mirror.

Fantastic! Thanks for testing.

from nist-data-mirror.