ent2ncr is very, very slow
|Reported by:||random||Owned by:||markjaquith|
I was playing with a profiler this afternoon, and was surprised to see that 10% of the request execution time was being spent on ent2ncr(). That's incredibly high.
The patch I'm about to attach replaces the 250+ str_replace() calls with a single one, which seems to be around 5-30x faster in real-world situations. The speed difference decreases as the length of text parsed increases. It was just a bit ahead at ~40,000 words of text, and the profiler choked on anything more.
Change History (8)
comment:3 markjaquith — 7 years ago
- Owner changed from anonymous to markjaquith
- Status changed from new to assigned