- HtmlDocumentBuilder : concatenation of strings instead of using String.format seems to improve time it takes to parse the document
- XmlRpcClient : use the XmlRpcClientLite if possible
- XmlRpcClient : create one instance (lazy init) (GreenPepperRepository, AtlassianRepository)
- DocumentBuilder : add a new method accepting the String html content (AtlassianRepository is creating a StringReader(content))
As seen in following screenshots, the execution time seems divided in two parts :
- Parsing the Html document
- Executing the specification
Then some issues where detected :
- GreenPepperRepository : IXmlRpcGreenPepperRepository GetProxy(string methodName) seems to take lot of cpu time first time it used.
Benchmark result on GreenPepper Core .NET :
Here is the command line :
Result : (dotnet profiler result source are here
)

Here is the command line :
Result : (dotnet profiler result source are here
)

Here is the command line :
(profiling has been stopped after three specifications executions)
Result : (dotnet profiler result source are here
)
