Grails

Improve GSP performance by reducing overhead of page binding (use new strategy which doesn't copy variables to each binding)

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.4-M1
  • Fix Version/s: 2.0-M1
  • Component/s: View technologies
  • Labels:
    None

Description

Issue for GSP optimizations shortly discussed here:
http://grails.1312388.n4.nabble.com/gsp-taglibs-td3546546.html#a3570147

The benchmark used in JTdev blog (http://www.jtict.com/blog/rails-wicket-grails-play-lift-jsp/) :
https://github.com/jtdev/blogpost_files/tree/master/grailsapp

It shows some bottlenecks which can be reduced by using a new strategy for handling page binding .

Issue Links

Activity

Hide
Lari Hotari added a comment -
Show
Lari Hotari added a comment - Commit: https://github.com/grails/grails-core/commit/0b0a36d7e045b4bab5dc6c0be12c35b877244fc9 In my test setup, these changes double the performance of the JTdev blog test app (https://github.com/jtdev/blogpost_files/tree/master/grailsapp) .
Hide
Stéphane Maldini added a comment -

I confirm the benefits from these changes, nice work!

Show
Stéphane Maldini added a comment - I confirm the benefits from these changes, nice work!
Hide
Stéphane Maldini added a comment -

changing <g:each> .each / .eachWithIndex to for(... in ...) form add 15% more performances

Show
Stéphane Maldini added a comment - changing <g:each> .each / .eachWithIndex to for(... in ...) form add 15% more performances
Hide
Stéphane Maldini added a comment -

GSP performances

Show
Stéphane Maldini added a comment - GSP performances

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: