A combo box with 80,000 entries in it is useless to the user regardless of memory issues!!! I don't know if there is a limit in the HTML but I'd say the *user* will reach a limit long before the *computer* ever will. I would say this has to be definitely < 1000 or better yet, < 100.
 
I can't say what sort of criteria you need to limit this without knowing what the application is. For example, if the person can be associated to a small number of these entries perhaps by a login and some form of association, like company or locality or something like that.
 
However, in general I would use one of two, or perhaps both, of these strategies:
 
1> On initial start-up present user with a text box into which a search term is entered by the user. When they press OK it limits the combo box to the matches. (if the matches are small enough number).
 
2> Use a straight Iterator pattern in which a list of 100 names (or other sufficiently small number like 10, 25, 50) a time are presented to the user. You can click 'next' to see the next lot of names, or select a name. When you click on a name you're effectively limiting the choice of name to one and presenting the form as before, this time without the combo.
 
3> better yet, front the Iterator pattern (2) with the search box (1).
 
We have similar sorts of problems in our app with the HUGE number of tradeable securities available on just 12 major world markets. We NEVER let a user see this list. After choosing the market and they want the user either has to know outright the correct symbol for the security they want or they can search on its name thereby allowing us to present a much smaller list from which they can select the appropriate one. It's slightly more complicated than that (the symbol can vary as there are several different symbologies available for securities such as RIC, ISIN, SEDOL, CUSIP, TICKER and so on plus you have securities which are traded in multiple markets and in some symbologies they have the same code and in others they will be different per market) but that's the general idea. Use search terms supplied by the user.
 
scot.
 
 
 -----Original Message-----
From: Satya [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 4 September 2002 16:38
To: JDJList
Subject: [jdjlist] Performance Issues

Hi,
 
  We are populating the customer names to combobox in our webapplication, the records fetched from database are more than 80,000.
When a single user tries to access this web page it gives a 'Out of memory' exception.
When the JVM heap memory is increased it worked fine. But it becomes very slow when running the loadrunner script.
simulating multiple users.
We are thinking of using some search criteria for fetching the customer names, thus reducing the no of records.
Any suggestions are appreciated..
 
Also,is there any limit on the number of values populated in a combo box in html?
 
Regards,
Satya
 
 
 
  
To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm
To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm

Reply via email to