Changes between Version 15 and Version 16 of MapGuideRfc110


Ignore:
Timestamp:
06/02/11 23:58:40 (14 years ago)
Author:
yangte
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MapGuideRfc110

    v15 v16  
    2424== Overview ==
    2525
    26 This RFC adds a !MgProfilingService which provides a skeleton for developers to profile existing !MapGuide APIs. !MgProfilingService aims to help developers and end users to identify resources that need to be optimized and performance bottlenecks. Two Profiling APIs will be implemented in this RFC and developers can add their own Profiling API into !MgProfilingService in the future
     26This RFC adds a !MgProfilingService which provides a skeleton for developers to profile existing !MapGuide APIs. !MgProfilingService aims to help developers and end users to identify resources that need to be optimized and performance bottlenecks. Two Profiling APIs will be implemented in this RFC and developers can add their own Profiling API into !MgProfilingService in the future. Also we will implement a UI in Site Admin to help the administrators easily execute a profiling and analyze the result.
    2727
    2828== Motivation ==
    2929
    30 Profiling APIs that would generate an XML report that could be analyzed to help determine if any resources need to be optimized or if there are performance bottlenecks in the code that need to be looked at.
     30Profiling APIs that would generate an XML report that could be analyzed to help determine if any resources need to be optimized or if there are performance bottlenecks in the code that need to be looked at. And The UI will offer an visual way to perform the profiling and review the result.
    3131
    3232== Proposed Solution ==
    … …  
    5353}}}
    5454
    55 Both of the above APIs will return an XML document that contains the profiling information gathered.
     55Both of the above APIs will return an XML document that contains the profiling information gathered. The UI will be implemented in Site Admin as a php web page. There will be input fields for the required parameters of a profiling. The parameters can also be encoded into the URL so that the profiling UI could be easily integrated with some custom application of !MapGuide.
     56After a profiling has finished with the input parameters, the result XML document will be returned and parsed.
     57Then the webpage will show the total render time for the map, and the render time of each layer in the map. Some additional layer information will be also showed to help the user analyze the results.The result could be exported as .csv file so that the user could do further analysis with other applications like Microsoft Excel.
    5658
    5759(We are not going to implement the Http API for !MgProfilingService)