You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
xml_text can take a long time when used with a large nodeset when trim is TRUE, and most of that time is spent calling sub twice for each node. One experience I had was getting the text for a nodeset with about 4.5 million nodes, where Rprof showed that calls to sub made up 72% of the nearly two minutes spent in xml_text.
hadley
added
upkeep
maintenance, infrastructure, and similar
feature
a feature request or enhancement
and removed
upkeep
maintenance, infrastructure, and similar
labels
Oct 30, 2023
xml_text
can take a long time when used with a large nodeset whentrim
isTRUE
, and most of that time is spent callingsub
twice for each node. One experience I had was getting the text for a nodeset with about 4.5 million nodes, whereRprof
showed that calls tosub
made up 72% of the nearly two minutes spent inxml_text
.I'll happily make a pull request if you'd like
Here's a brief demo showing time saved:
The text was updated successfully, but these errors were encountered: