Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Loading Lists

Updated: 22 May 2010 | 5 comments
Dalceon's picture
+1 1 Vote
Login to vote

Does anyone have recommendations for loading large lists?
For example if I need to load a list of employees at the company.

When I debug generally the lists load ok, but when I publish it may take a minue to load a list with 900 items.
this would be unacceptable to the end user so any suggestions would be greatly appreciated.
The database select it self doesn't seem to be slow, just when Workflow appears to be creating the objects.

I don't want the end user to have to search everytime they need to fill in a name on a form.
 

discussion Filed Under:

Comments

reecardo's picture
30
Apr
2009
0 Votes 0
Login to vote

Are you doing the fetch

Are you doing the fetch BEFORE entering the form, or are the items in the form's dropdown hooked up to a custom model that does a fetch? You should definitely do the "intense" thing before entering the form, then just using configurable filters on the fetched list to show the appropriate data once inside the form.

Dalceon's picture
30
Apr
2009
0 Votes 0
Login to vote

that's how I'm doing it, but

that's how I'm doing it, but it takes 20-30 times to load in production.
the development env and the production are on the same machine.
it loads in about 1 second in test and takes about 30 to load when I publish the project.

I have taken the data from the sql server, and played with the persistant file storage.
it greatly decreased the time in dev, but not too much affect in production.

ChrisBern's picture
01
May
2009
0 Votes 0
Login to vote

Which generator are you using?

Which generator are you using to load the data?  It sounds like you might be using the Query/Script Generator, but I'm just guessing.

It might be a worthwhile test to try a different generator than the one you're using, even though you mentioned that the SQL side didn't seem to be the part slowing you down.  For example, if you're using a Table Generator, try using a Query/Script Generator, or if you're using the Query/Script Generator, try putting it in a stored procedure and calling it through the Stored Procedure Generator.  Stored procedures can be significantly faster and more efficient because they are pre-compiled and run on the SQL server. 

From the way you've described the scenario, chances are there may not be a significant difference between one method and the next, but to me it would be worth a few minutes to try.  Good luck and let us know if you come up with anything that helps...

XIANRAIN's picture
03
May
2009
1 Vote -1
Login to vote

Hi Dalceon kindly provide the

Hi Dalceon kindly provide the details needed for us to better process and come up with the best solution.

Thanks,

XianRain

Dalceon's picture
04
May
2009
0 Votes 0
Login to vote

I installed workflow server

I installed workflow server on another box and published there.  It seems to run better even through the hardware is less than the current system.
My current dev environment is in a vm, but I'm not sure if that's the cause of the issue.
I'm going to wipe the installation and try again.  perhaps something go goofy with the installation.