Performance problem with large map files

Question

Performance problem with large map files

Closed this issue 8 years ago · 0 comments

Termit1975 commented 8 years ago

I'm using new option from 1.1.5 (cacheGlobally=true) but still have a performance issue. When converting a stack trace that links to a large map file many times, Chrome profiler shows that almost all the time is spent in SourceMapConsumer quick sorting source map entries. Keeping the SourceMapConsumer in the cache instead of the source map string will fix the issue.

I will issue a pull request for this issue.