Hi -

Also on Stack Exchange to spread the good word:
http://stackoverflow.com/questions/27930539/concurrent-read-access-to-thread-object-that-emulates-map

I am experiencing (very) slow page load times that increase proportionately
to the number of active users on the system. I have a hunch that this is
related to a custom defined thread object:

define stageStoreCache => thread {
parent map
public oncreate() => ..oncreate()
}

This stageStoreCache object simply mimics the behavior of a map whose data
available across the entire instance.

Many threads are reading it and very few threads are writing to it. Is this
a poorly conceived solution to having a large map of data available across
the instance? It's a fairly large map of maps that when exported to
map->asstring can exceed 5MB. The objective is to prevent translating data
stored as JSON in the database to Lasso types on the fly.

It seems that the large size of the stageStoreCache is not what causes
problems. It seems to really be the number of concurrent users on the
system.

Thanks for any insight you can offer.

-Justin

#############################################################

This message is sent to you because you are subscribed to
the mailing list Lasso Lasso@lists.lassosoft.com
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
Send administrative queries to <Lasso-request@lists.lassosoft.com>