Santiago Gala wrote:
[EMAIL PROTECTED] wrote:
I'm not sure how a MRU cache would perform under high load, with
some ten-thousands of concurrent users on an app server with a big
thread pool running on a multi-processor machine - there might be
synchronization issues resulting in
[EMAIL PROTECTED] wrote:
Santiago Gala wrote:
[EMAIL PROTECTED] wrote:
I'm not sure how a MRU cache would perform under high load, with
some ten-thousands of concurrent users on an app server with a big
thread pool running on a multi-processor machine - there might be
[EMAIL PROTECTED] wrote:
Raphael Luta wrote:
[EMAIL PROTECTED] wrote:
Whether it is better to store the PSML reference in a session or in
some
other data structure depends on the portal usage pattern. We envision a
usage
pattern where a large number of users accesses the
Raphael Luta wrote:
[EMAIL PROTECTED] wrote:
Whether it is better to store the PSML reference in a session or in
some
other data structure depends on the portal usage pattern. We envision a
usage
pattern where a large number of users accesses the portal mostly
between 0
and 5
Raphael Luta wrote:
[EMAIL PROTECTED] wrote:
Raphael Luta wrote:
There's a good reason why the PSML is not in the session : a PSML file is
not necessarily equal to one user. The mapping between PSML files and
User
is done by the Profiler, which can be implemented in a lot
-Original Message-
From: Raphael Luta [mailto:[EMAIL PROTECTED]]
Sent: Sonntag, 12. November 2000 23:26
To: JetSpeed
Subject: Re: Scalability problem in PortletSetFactory ?
Santiago Gala wrote:
[EMAIL PROTECTED] wrote:
There seems to be a scalability problem
[EMAIL PROTECTED] wrote:
There seems to be a scalability problem in the PortletSetFactory:
For each user, a PortletSetFactory object is created that holds a Portlets
tree
representing the user's PSML file. I guess the tree can become quite big in
terms
of memory usage.
It is very funny
[EMAIL PROTECTED] wrote:
There seems to be a scalability problem in the PortletSetFactory:
For each user, a PortletSetFactory object is created that holds a Portlets
tree
representing the user's PSML file. I guess the tree can become quite big in
terms
of memory usage.
It is very funny
Santiago Gala wrote
[EMAIL PROTECTED] wrote:
There seems to be a scalability problem in the PortletSetFactory:
For each user, a PortletSetFactory object is created that holds a
Portlets
tree
representing the user's PSML file. I guess the tree can become quite
big in
terms
There seems to be a scalability problem in the PortletSetFactory:
For each user, a PortletSetFactory object is created that holds a Portlets
tree
representing the user's PSML file. I guess the tree can become quite big in
terms
of memory usage.
The PortletSetFactory object is stored
10 matches
Mail list logo
