IssueTracker

A short description of the request:

I would like to propose improving the process cost of XmlService of Google Apps Script as a future request.

What is the purpose of this new feature?

When I have created an application using XmlService with Google Apps Script, I have felt the high process cost of XmlService. When I measured this, it was found that under enabling V8 runtime, the process cost of XmlService is much higher than those of "cheerio" and the simple script using regex. You can see my report at here.

From my experiment, I guessed that this high process cost of XmlService might be due to the that XmlService is run in the internal serverside, while a simple script using regex is run with the script editor under enabling V8 runtime. And, unfortunately, I cannot improve the process cost in this case.

I think that Class XmlService is very useful for managing XML data. For example, Class XmlService can not only parse and read XML data but also update XML data and create new XML data. When the process cost of XmlService is reduced, the process cost of both new applications and the existing applications created by Google Apps Script including XmlService can be also reduced. (For example, this Google Apps Script library can compensate the processes that they services cannot achieve using XmlService. Ref This process cost can be also reduced, if this future request was achieved.) This leads to a lower cost of the script and handling XML data. From these situations, I would like to propose reducing the process cost of Class XmlService.