mirror of
https://github.com/brutaldev/StrongNameSigner.git
synced 2026-04-25 11:26:04 +03:00
[GH-ISSUE #24] Poor performance #21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @stevenxi on GitHub (Jun 29, 2016).
Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/24
Originally assigned to: @brutaldev on GitHub.
Hi,
I've tried to sign big batch of assemblies in one go (400+). It doesn't finish within 30 mins.
I've add an extra method in SigningHelper to solve this issue: it allows you solve references as join rather than 2 loop matching
@brutaldev commented on GitHub (Jun 29, 2016):
Please create a pull request for this change.
@stevenxi commented on GitHub (Jun 29, 2016):
Have no git client here. And I'm not familiar with git.
On Wed, Jun 29, 2016 at 5:32 PM, Werner van Deventer <
notifications@github.com> wrote:
@brutaldev commented on GitHub (Jun 29, 2016):
I'm sorry, but I have no idea where you expect me to put this code. It doesn't replace an existing method and I have zero proof that it makes any difference to the performance. Disk I/O against 400+ files is more than likely the problem, you should probably just isolate the files you actually want to sign rather than pointing to a giant directory.
@stevenxi commented on GitHub (Jun 29, 2016):
I'm not expecting you to put this code to your code base, just let you know
there's a problem and provide the solution.
Feel free leave the code without change. It works fine, just slow in some
cases.
But just let you know my change speed up the same process (400+ files) to
15 seconds, as most of them are already signed. The performance bottle neck
is when updating referencing.
On Wed, Jun 29, 2016 at 5:37 PM, Werner van Deventer <
notifications@github.com> wrote:
@brutaldev commented on GitHub (Sep 1, 2016):
Will look into large numbers of files at some point, this doesn't affect many (if any) users. As for the double check, reliability trumps performance here so leaving it as is for now.
@brutaldev commented on GitHub (Sep 17, 2016):
Added definition caching which massively improves the performance when dealing with a lot of assemblies. These changes were released in v2.0.0.