Hi,

I've noticed that list box and searchable list box initialisation performance is considerably slower when a protocol is run in the webport than the client.

I've attached a simple example of this. A list box reads in 10K rows for a user to select something. It then creates a couple of other input boxes.

When run from the client the protocol opens up in internet explorer and is usable in < 1 second.

However if the same protocol is run in the webport it takes 8 seconds for the list box to initialise and the next 2 boxes to appear.

I don't understand why the same protocol exhibits such different behaviour. It appears to be linked to the number of rows as the webport initialisation time increases as the number of rows increase.

I realise that a list box with 10000 entries is not much use. However we have a (Fast) version of the Searchable list box which can handles 10Ks of rows and search without performance loss (also included in the protocol - feel free to use if it’s useful). However this (fast) searchable list box exhibits the same slow initialisation on the webport but not the client.

The common factor seems to be the standard Accelrys list box component. However I'm not able to dig any further in it to try and pin point why it’s so much slower in the webport.

Perhaps someone from the Accelrys/Biovia team could take a look at the list box code to see what’s happening and fix?

Thanks

Joe