sparklemotion/nokogiri

investigate #1970 - string optimization

Open

#1986 opened on Feb 3, 2020

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Ruby (5,615 stars) (806 forks)batch import
help wantedneeds/researchtopic/performance

Description

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