• Post Reply Bookmark Topic Watch Topic
  • New Topic

576 radio buttons on one page. Performance issues.  RSS feed

 
Eddy Dean
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello everyone,

In an application I'm currently creating there is one page that has 576 <t:radio> items on it, and it didn't really surprise me that rendering this page took over 5 seconds on a fairly modern computer.

All radio items are nested in an unordered list, which can be collapsed and expanded through Javascript.

The problem is not the browser, it just takes the server this long to render the page. Is there any way to make this faster?

Obviously this load time is not acceptable, which is why I'm considering to use a tomahawk tree instead. How would tree component do with this many nodes? Would it be just as slow, or have a more acceptable rendering time? The radio buttons are three 'levels' deep in the tree. The first branch has 16 nodes, second branch has 6 nodes and third branch has 6 nodes (giving 16*6*6=576 leafs total).

Other solutions are of course also welcome, but I'd rather not use anything that requires Javascript, optional javascript is okay.

Thanks a lot for helping,

Eddy Dean
 
Sean Clark
Rancher
Posts: 377
Android Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hey,

why not display only the <t:radio> that are displyed when the page loads and remove others into seperate jsps that you can then load into place using javascript when necessary?

Sean
 
Eddy Dean
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If I understand it correctly you are suggesting an ajax-like approach (but with HTML instead of XML). This will not work in my situation, because I want the page to work without javascript as well. My solution shows all the choices when javascript is disabled (which is not great, because it's a really long list).

The tomahawk tree component looks promising, but I wonder how it'll hold up when there are this many nodes.

Thanks for your reply anyway

Of course it's also possible that the JSF RI is a lot faster than MyFaces (could also be the other way around, I honestly have no idea), but I rather not spend my time changing implementations all the time.

- Eddy
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!