Question Webspeed get-value taking more time

Muthu11

New Member
Hi,

I'm trying to build a webspeed application. My webpage has more than 3000 elements in a single form and the form submits to same page for some user actions. I used get-value function to get those element values and build the web pages. For some customers it completes in seconds but for others it takes minutes to complete all get-value functions. when I removed some 20 hidden elements it is fast for all the customers.

Could someone tell me what is wrong here and how could it be fixed?

Thanks in advance.
 

TomBascom

Curmudgeon
3,000 elements in a single form sounds wrong all by itself. I'm having a hard time imagining what you could be doing that requires that.

Beyond that observation -- perhaps you could start removing each of the 20 hidden elements until you determine which one(s) is actually responsible. Once you know that you might be able to either recognize what is special about that or add more instrumentation to figure out why the problem elements are slow.
 

Muthu11

New Member
My application is new customer enrollment. So the form has all elements that needs to enroll a customer like name, address, nominees, etc.. so there's a 3000 elements in the form.

I'm also trying to store a temp-table tterrors and all its fields as hidden elements in the form. So I can build the temp table when the page reloads. This is where I'm facing the problem. Till 10 errors it's working fine if it's more than 10 page starts slowing down. Number of safe errors also vary from customer to customer.

Not only get-value of tterrors is slow, but all get-value function call starts becoming 12 times slower.. seems like browser couldn't parse HTML elements easily and get the value quicker.

Do we have any limitations on number of elements in a form? Or size of the HTML page etc?
 

Muthu11

New Member
3,000 elements in a single form sounds wrong all by itself. I'm having a hard time imagining what you could be doing that requires that.

Beyond that observation -- perhaps you could start removing each of the 20 hidden elements until you determine which one(s) is actually responsible. Once you know that you might be able to either recognize what is special about that or add more instrumentation to figure out why the problem elements are slow.
My application is new customer enrollment. So the form has all elements that needs to enroll a customer like name, address, nominees, etc.. so there's a 3000 elements in the form. Currently this is built in Java struts and I'm trying to rebuild in webspeed.

I'm also trying to store a temp-table tterrors and all its fields as hidden elements in the form. So I can build the temp table when the page reloads. This is where I'm facing the problem. Till 10 errors it's working fine if it's more than 10 page starts slowing down. Number of safe errors also vary from customer to customer.

Not only get-value of tterrors is slow, but all get-value function call starts becoming 12 times slower.. seems like browser couldn't parse HTML elements easily and get the value quicker.

Do we have any limitations on number of elements in a form? Or size of the HTML page etc?
 

TomBascom

Curmudgeon
I'm pretty sure that if I needed 3,000 data elements to enroll a customer that I would never need to worry about having any new customers.

Anyhow, as I mentioned above, I think you need to break down the problem into something smaller and more focused that you can instrument to determine where the issues are.

As a kind of general observation (outside of the obvious bit regarding 3,000 elements) if something becomes a problem after X iterations it is probably due to either data growth (the number of entries and the size thereof in the temp-table) or poor memory management (IOW you dynamically create stuff but fail to delete it).
 
Top