sparklemotion/nokogiri

investigate #1970 - string optimization

Open

#1.986 geöffnet am 3. Feb. 2020

Auf GitHub ansehen
 (5 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)Ruby (806 Forks)batch import
help wantedneeds/researchtopic/performance

Repository-Metriken

Stars
 (5.615 Stars)
PR-Merge-Metriken
 (Keine gemergten PRs in 30 T)

Beschreibung

Background

PR #1970 was opened by @ashmaroli to attempt to reduce the number of allocated empty strings created by Nokogiri.

This PR was merged and released in v1.11.0.rc1.

@ashmaroli repeated his profiling (I think using the memory_profiler gem) and commented that it didn't seem to have an effect.

Actions

  1. reproduce the original memory profliling scenario - @ashmaroli please help with this
  2. determine whether the patch can be tweaked to reduce the number of allocated strings or no
  3. make a recommendation - revert or re-patch

Retrospecting

I should have asked for more details from @ashmaroli when he submitted the PR to reproduce his results, and demonstrate improvement, before merging. This would have allowed me to ask questions at a more appropriate time.

Contributor Guide