This is common in many testing scenarios, enabling user data to hang around in memory until the user session times out, or until any caches in use get refreshed.
在许多测试场景中，这是很常见的，允许用户数据挂起在内存中，直到用户会话超时，或者直到刷新正在使用的任何缓存。
Presence of a large number of objects of these types could also signify a deeper memory leak where application objects held by these session objects are actually leaking.
存在大量的此类对象还意味着更深一层的内存泄漏，即由这些会话对象保留的应用程序对象实际上正在泄漏。
The database session stores these query logs in memory and periodically commits the local history to disk.
数据库会话在内存中保存这些查询日志，并定期将本地历史写入磁盘。
Basically, you can configure how often the session manager writes to the database or to the peer server's memory.
基本上来说，在其中可以配置会话管理器写到数据库或对等服务器的内存的频率。
Each extra session requires extra memory for its backups on every node in the cluster, so you quickly run out of memory.
每个额外节点都需要额外的内存来保存集群中每个节点的备份，所以很快就会用光内存。
For example, applications should not put too much data into sessions to reduce the memory footprint of the server and to make session persistence easier and faster.
例如，应用程序不应将过多的数据放置到会话中，从而减少服务器的内存占用并更快速方便地保持会话。
If no maximum limit is set on the maximum number of session objects that can be held in memory, then it is possible to have many session objects during peak user load time.
如果不对内存中可以保持的会话对象的最大数量设置最大限制，那么在用户加载高峰期，可能有许多会话对象。
Since the parameter is not maintained in the URL, it needs to be stored in the session (even in the case of anonymous use) and therefore impacts portal server memory consumption.
由于参数不能保存在URL中，而要保存在会话中(即使在异步使用情况下)，因而影响门户服务器内存消耗。
Large session objects decrease the JVM memory available for creation and execution of application objects.
大型的会话对象会减少可用以创建和执行应用程序对象的JVM内存。
Each session context is very memory intensive, which means that ten times more memory would have to be allocated to accommodate each session context.
每个会话上下文都是内存密集型的，这意味着十倍以上的内存将被分配，以容纳每一个会话上下文。
Instead, use an in memory hash table to cache the data and just keep a key to the data in the session.
相反地，应该使用内存中的哈希表来缓存数据，并且在会话中保存一个对此数据进行引用的键。
The problem can get worse if the session contains more and more data and thus requires more memory.
如果会话包含越来越多的数据，从而要求使用更多的内存，则会进一步使问题严重化。
Otherwise, the session will persist until it expires, which will consume memory, potentially for a long time, depending on the session expiration timeout.
否则，会话将持久化直到它失效，这会消耗内存，并且可能是长时间的(取决于会话超时时间)。
If you're not careful, the browser's memory demands will grow over the duration of a browsing session.
如果不小心，浏览器的内存需求将在整个浏览会话周期中不断增加。
In the event of a failure, access to the session data will be faster, since it is in memory, and the data itself remains highly available.
在失败发生时，对会话数据的访问将更快，因为它位于内存中，数据本身也高度可用。
Sometimes this may just be a session id of some sort that can be used to retrieve server-side state from memory or a database.
有时候这仅仅是某种类型的会话id，它可以用来从内存或数据库检索服务器端状态。
When the service is active, an ASP.NET application can be configured to store any session information into the memory of this process.
当服务激活，可以配置ASP.NET应用将会话信息保存在该进程的内存中。
We first retrieve the session ID to create a unique name for our named memory. We then try to get access to it.
我们首先检索会话id，以便为我们的已命名内存创建一个惟一名称。
Cache entries can be scoped with the session ID to keep a relationship between the session and the data that is to be kept in memory.
可以使用会话id设置缓存条目的范围，以使会话和要保存在内存中的数据建立关联。
We reuse the ABAP VM as much as possible for things such as garbage collection, session handling, memory management, etc.
我们尽可能地重用ABAPVM来实现垃圾回收、会话处理、内存管理等。
J2EE applications typically store this kind of data in in-memory session objects for better performance and for a better user experience.
J2EE应用程序通常将此类信息存储在内存中的会话对象中，以实现更好的性能或实现更好的用户体验。
Every session consumes server resources (specifically memory) that must be reclaimed if the session times out.
但每个会话都消耗服务器资源(特别是内存)，这些资源必须在会话超时时收回。
This will reduce the serialized size of a session, but will not change the in-memory size, which also has an impact on how efficiently an application server can handle sessions.
这将降低会话的序列化后的大小，但不会更改内存的大小，而这对应用程序服务器处理会话的效率也有影响。
There are many type of advice provided through this facility, including pool setting advice for ORB and Web pools, session setting advice, memory leak detection or even data source diagnostic advice.
这一工具可以提供多种类型的建议，包括对OR b和we b池的池设置的建议，对会话设置的建议，对内存泄漏的建议，甚至包括对数据源的诊断建议。
Stateful session beans consume a substantial amount of the container's time and memory.
有状态会话bean消耗了容器的大量时间和内存。
Those services are DynaCache, memory to memory session replication, core groups, Web services caching, and stateful session bean persistence.
这些服务是DynaCache、内存到内存会话复制、核心组、Web服务缓存和有状态会话Bean持久性。
This loading takes a long time both because of network bandwidth overhead and session cache overhead (memory consumption and GC pause) if your Hibernate session is stateful.
这种加载需要很多时间，既有网络带宽的原因，如果Hibernate的会话是有状态的，其中也会有会话缓存的原因(内存消耗和GC暂停)。
Just a number in the NAME column is the session id since memory pools for a session are tracked by session id.
name列中的数字是会话id，因为会话的内存池是按会话id跟踪的。
Just a number in the NAME column is the session id since memory pools for a session are tracked by session id.
name列中的数字是会话id，因为会话的内存池是按会话id跟踪的。
应用推荐