high_scalability high_scalability-2007 high_scalability-2007-97 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: Hi, Every application server has its own session management implementations for supporting high scalability. But an application architect/developer has to design and implement the application to make the best use of it. What are the guiding principles and pattern for session state management? Websphere System management red book mentions that "Session management performance is optimum when session data per user is around 2Kb. It degrades if session data is more than that". I have following questions. 1. How do you measure session data per user? 2. It is generally recommended that you should keep all the session state in database and keep only the keys in HttpSession object. Then everytime a web request is processed, session data is fetched from the database. This way all the data remains in memory only till the request is processed and actual data in HttpSession is very less. (Only few keys). What is the general practice? At what point you should be switching fr
sentIndex sentText sentNum sentScore
1 Hi, Every application server has its own session management implementations for supporting high scalability. [sent-1, score-1.004]
2 But an application architect/developer has to design and implement the application to make the best use of it. [sent-2, score-0.235]
3 What are the guiding principles and pattern for session state management? [sent-3, score-0.972]
4 Websphere System management red book mentions that "Session management performance is optimum when session data per user is around 2Kb. [sent-4, score-1.671]
5 It is generally recommended that you should keep all the session state in database and keep only the keys in HttpSession object. [sent-10, score-1.174]
6 Then everytime a web request is processed, session data is fetched from the database. [sent-11, score-1.058]
7 This way all the data remains in memory only till the request is processed and actual data in HttpSession is very less. [sent-12, score-0.76]
8 At what point you should be switching from keeping data in HttpSession to database? [sent-15, score-0.316]
9 Is there any open source framework which helps you do session management in a way mentioned in point no. [sent-18, score-1.122]
wordName wordTfidf (topN-words)
[('session', 0.568), ('httpsession', 0.49), ('management', 0.199), ('processed', 0.162), ('everytime', 0.156), ('optimum', 0.156), ('keys', 0.153), ('guiding', 0.15), ('fetched', 0.138), ('websphere', 0.138), ('degrades', 0.123), ('mentions', 0.118), ('recommended', 0.111), ('request', 0.105), ('remains', 0.1), ('red', 0.098), ('state', 0.097), ('implementations', 0.093), ('switching', 0.092), ('data', 0.091), ('mentioned', 0.087), ('ebay', 0.087), ('till', 0.084), ('principles', 0.082), ('book', 0.081), ('actual', 0.075), ('pattern', 0.075), ('supporting', 0.072), ('application', 0.072), ('practice', 0.072), ('generally', 0.071), ('point', 0.071), ('follow', 0.068), ('keep', 0.066), ('measure', 0.066), ('user', 0.064), ('keeping', 0.062), ('following', 0.06), ('per', 0.059), ('general', 0.057), ('framework', 0.056), ('implement', 0.056), ('websites', 0.054), ('helps', 0.053), ('way', 0.052), ('database', 0.042), ('around', 0.038), ('amazon', 0.037), ('source', 0.036), ('best', 0.035)]
simIndex simValue blogId blogTitle
same-blog 1 0.99999994 97 high scalability-2007-09-18-Session management in highly scalable web sites
Introduction: Hi, Every application server has its own session management implementations for supporting high scalability. But an application architect/developer has to design and implement the application to make the best use of it. What are the guiding principles and pattern for session state management? Websphere System management red book mentions that "Session management performance is optimum when session data per user is around 2Kb. It degrades if session data is more than that". I have following questions. 1. How do you measure session data per user? 2. It is generally recommended that you should keep all the session state in database and keep only the keys in HttpSession object. Then everytime a web request is processed, session data is fetched from the database. This way all the data remains in memory only till the request is processed and actual data in HttpSession is very less. (Only few keys). What is the general practice? At what point you should be switching fr
2 0.31577396 240 high scalability-2008-02-05-Handling of Session for a site running from more than 1 data center
Introduction: If using a DB to store session(used by some app server, ex.. websphere), how would an enterprise class site that is housed in 2 different data centers(that are live/live) maintain the session between both data centers. The problem as I see it is that since each data center has their own session database, if I was to flip the users to only access Data Center 1(by changing the DNS records for the site or some other Load balancing technique) then that would cause all previous Data Center 2 users to lose their session. What would be some pure hardware based solutions to this that are being used now? That way the applications supporting the web site can be abstracted from this. As I see now, a solution is to possibly have the session databases in both centers some how replicate the data to each other. I just don't see the best way to even accomplish this you are not even guraunteed that the session ID's will be unique since it's 2 different Application Server tiers(again websphere)
3 0.23421051 472 high scalability-2008-12-19-How to measure memory required for a user session
Introduction: hi, What are the practices followed, tools used to measure session memory requirement per user? Thanks, Unmesh
4 0.17544451 565 high scalability-2009-04-13-Benchmark for keeping data in browser in AJAX projects
Introduction: Hi, We are using AJAX and see a lot of opportunity to keep session state on client browser with javascript objects. Is there any benchmark about how much data you can generally keep in javascript objects in browser? Thanks, Unmesh
5 0.16131099 1126 high scalability-2011-09-27-Use Instance Caches to Save Money: Latency == $$$
Introduction: In the post Using memcache might be free, but it's costing you money with instance pricing! Use instance caches if possible made on the Google App Engine group, Santiago Lema brings up an oldie but a goody of an idea that was once used to improve performance, but now it's used to save money : Santiago's GAE application went from about $9 to about $177 per month. Memcache is slow enough that under higher loads extra instances are created by the scheduler to handle the load. For static or semi-static data, a way around the cost of the extra instances, is to keep a cache in the instance so requests can be served out of local memory rather than going to memcache or the database. A simple hashtable makes a good in-memory cache. This solution made his app affordable again by reducing the number of instances back to 1 (sometimes 2). Where have we seen this before? This is a variant of the old Sticky Session idea where web sessions are stored in RAM in an application ser
6 0.14913902 1565 high scalability-2013-12-16-22 Recommendations for Building Effective High Traffic Web Software
7 0.14629866 388 high scalability-2008-09-23-Event: CloudCamp Silicon Valley Unconference on 30th September
8 0.13276917 115 high scalability-2007-10-07-Using ThreadLocal to pass context information around in web applications
9 0.11679672 542 high scalability-2009-03-17-IBM WebSphere eXtreme Scale (IMDG)
10 0.10999719 207 high scalability-2008-01-10-Sharding with Cookie-Based Session Storage
11 0.10380509 427 high scalability-2008-10-22-Server load balancing architectures, Part 2: Application-level load balancing
12 0.100055 392 high scalability-2008-09-24-Building a Scalable Architecture for Web Apps
13 0.092085063 1284 high scalability-2012-07-16-Cinchcast Architecture - Producing 1,500 Hours of Audio Every Day
14 0.085123517 1405 high scalability-2013-02-13-7 Sensible and 1 Really Surprising Way EVE Online Scales to Play Huge Games
15 0.083763316 1205 high scalability-2012-03-07-Scale Indefinitely on S3 With These Secrets of the S3 Masters
16 0.079333223 638 high scalability-2009-06-26-PlentyOfFish Architecture
17 0.079098187 188 high scalability-2007-12-19-How can I learn to scale my project?
18 0.078458324 1361 high scalability-2012-11-22-Gone Fishin': PlentyOfFish Architecture
19 0.076299816 232 high scalability-2008-01-29-When things aren't scalable
20 0.073861763 331 high scalability-2008-05-27-eBay Architecture
topicId topicWeight
[(0, 0.113), (1, 0.017), (2, -0.028), (3, -0.042), (4, -0.008), (5, 0.023), (6, 0.028), (7, -0.036), (8, -0.032), (9, 0.017), (10, 0.007), (11, 0.052), (12, -0.044), (13, 0.011), (14, -0.021), (15, -0.031), (16, 0.011), (17, 0.016), (18, 0.083), (19, -0.014), (20, -0.005), (21, -0.018), (22, 0.017), (23, -0.033), (24, -0.025), (25, -0.057), (26, -0.04), (27, -0.007), (28, -0.02), (29, 0.031), (30, 0.03), (31, 0.025), (32, 0.054), (33, -0.047), (34, -0.002), (35, 0.0), (36, 0.035), (37, 0.025), (38, 0.03), (39, -0.01), (40, -0.0), (41, 0.104), (42, 0.079), (43, 0.129), (44, 0.082), (45, 0.013), (46, 0.007), (47, -0.038), (48, -0.042), (49, 0.023)]
simIndex simValue blogId blogTitle
same-blog 1 0.92687309 97 high scalability-2007-09-18-Session management in highly scalable web sites
Introduction: Hi, Every application server has its own session management implementations for supporting high scalability. But an application architect/developer has to design and implement the application to make the best use of it. What are the guiding principles and pattern for session state management? Websphere System management red book mentions that "Session management performance is optimum when session data per user is around 2Kb. It degrades if session data is more than that". I have following questions. 1. How do you measure session data per user? 2. It is generally recommended that you should keep all the session state in database and keep only the keys in HttpSession object. Then everytime a web request is processed, session data is fetched from the database. This way all the data remains in memory only till the request is processed and actual data in HttpSession is very less. (Only few keys). What is the general practice? At what point you should be switching fr
2 0.73684877 240 high scalability-2008-02-05-Handling of Session for a site running from more than 1 data center
Introduction: If using a DB to store session(used by some app server, ex.. websphere), how would an enterprise class site that is housed in 2 different data centers(that are live/live) maintain the session between both data centers. The problem as I see it is that since each data center has their own session database, if I was to flip the users to only access Data Center 1(by changing the DNS records for the site or some other Load balancing technique) then that would cause all previous Data Center 2 users to lose their session. What would be some pure hardware based solutions to this that are being used now? That way the applications supporting the web site can be abstracted from this. As I see now, a solution is to possibly have the session databases in both centers some how replicate the data to each other. I just don't see the best way to even accomplish this you are not even guraunteed that the session ID's will be unique since it's 2 different Application Server tiers(again websphere)
3 0.73081613 472 high scalability-2008-12-19-How to measure memory required for a user session
Introduction: hi, What are the practices followed, tools used to measure session memory requirement per user? Thanks, Unmesh
4 0.58265805 346 high scalability-2008-06-28-ID generation schemes
Introduction: Hi, Generating unique ids is a common requirements in many projects. Generally, this responsibility is given to Database layer. By using sequences or some other technique. This is a problem for horizontal scalability. What are the Guid generation schemes used in high scalable web sites generally? I have seen use java's SecureRandom class to generate Guid. What are the other methods generally used? Thanks Unmesh
5 0.57977098 188 high scalability-2007-12-19-How can I learn to scale my project?
Introduction: This is a question asked on the ycombinator list and there are some good responses. I gave a quick response, but I particularly like neilk's knock out of the park insightful answer: Read Cal Henderson's book. (I'd add in Theo's book and Release It! too) The center of your design should be the data store, not a process. You transition the data store from state to state, securely and reliably, in small increments. Avoid globals and session state. The more "pure" your function is, the easier it will be to cache or partition. Don't make your data store too smart. Calculations and renderings should happen in a separate, asynchronous process. The data store should be able to handle lots of concurrent connections. Minimize locking. (Read about optimistic locking). Protect your algorithm from the implementation of the data store, with a helper class or module or whatever. But don't (DO NOT) try to build a framework for any conceivable query. Just the ones your algorithm needs. V
6 0.56843531 565 high scalability-2009-04-13-Benchmark for keeping data in browser in AJAX projects
7 0.53714663 1565 high scalability-2013-12-16-22 Recommendations for Building Effective High Traffic Web Software
8 0.53127515 1160 high scalability-2011-12-21-In Memory Data Grid Technologies
9 0.52766663 1284 high scalability-2012-07-16-Cinchcast Architecture - Producing 1,500 Hours of Audio Every Day
10 0.52608716 681 high scalability-2009-08-16-TechDev Stages
11 0.52560461 822 high scalability-2010-05-04-Business continuity with real-time data integration
12 0.52260828 421 high scalability-2008-10-17-A High Performance Memory Database for Web Application Caches
13 0.5204072 207 high scalability-2008-01-10-Sharding with Cookie-Based Session Storage
14 0.51568091 202 high scalability-2008-01-06-Email Architecture
15 0.51358181 633 high scalability-2009-06-19-GemFire 6.0: New innovations in data management
16 0.51142949 440 high scalability-2008-11-11-Arhcitecture for content management
17 0.51081693 500 high scalability-2009-01-22-Heterogeneous vs. Homogeneous System Architectures
18 0.50597852 684 high scalability-2009-08-18-Real World Web: Performance & Scalability
19 0.50596857 396 high scalability-2008-09-26-Lucasfilm: The Real Magic is in the Data Center
20 0.50542885 388 high scalability-2008-09-23-Event: CloudCamp Silicon Valley Unconference on 30th September
topicId topicWeight
[(1, 0.136), (2, 0.275), (10, 0.053), (30, 0.015), (40, 0.273), (61, 0.022), (79, 0.049), (89, 0.036)]
simIndex simValue blogId blogTitle
1 0.97669595 402 high scalability-2008-10-05-Paper: Scalability Design Patterns
Introduction: I have introduced pattern languages in my earlier post on The Pattern Bible for Distributed Computing . Achieving highest possible scalability is a complex combination of many factors. This PLoP 2007 paper presents a pattern language that can be used to make a system highly scalable. The Scalability Pattern Language introduced by Kanwardeep Singh Ahluwalia includes patterns to: Introduce Scalability Optimize Algorithm Add Hardware Add Parallelism Add Intra-Process Parallelism Add Inter-Porcess Parallelism Add Hybrid Parallelism Optimize Decentralization Control Shared Resources Automate Scalability
2 0.97033256 1419 high scalability-2013-03-07-It's a VM Wasteland - A Near Optimal Packing of VMs to Machines Reduces TCO by 22%
Introduction: In Algorithm Design for Performance Aware VM Consolidation we learn some shocking facts (gambling in Casablanca?): Average server utilization in many data centers is low, estimated between 5% and 15%. This is wasteful because an idle server often consumes more than 50% of peak power. Surely that's just for old style datacenters? Nope. In Google data centers, workloads that are consolidated use only 50% of the processor cores. Every other processor core is left unused simply to ensure that performance does not degrade. It's a VM wasteland. The goal is to reduce waste by packing VMs onto machines without hurting performance or wasting resources. The idea is to select VMs that interfere the least with each other and places them together on the same server. It's a NP-Complete problem, but this paper describes a practical method that performs provably close to the optimal. Interestingly they can optimize for performance or power efficiency, so you can use different algorithm
3 0.96262634 1471 high scalability-2013-06-06-Paper: Memory Barriers: a Hardware View for Software Hackers
Introduction: It's not often you get so enthusiastic a recommendation for a paper as Sergio Bossa gives Memory Barriers: a Hardware View for Software Hackers : If you only want to read one piece about CPUs architecture, cache coherency and memory barriers, make it this one. It is a clear and well written article. It even has a quiz. What's it about? So what possessed CPU designers to cause them to inflict memory barriers on poor unsuspecting SMP software designers? In short, because reordering memory references allows much better performance, and so memory barriers are needed to force ordering in things like synchronization primitives whose correct operation depends on ordered memory references. Getting a more detailed answer to this question requires a good understanding of how CPU caches work, and especially what is required to make caches really work well. The following sections: present the structure of a cache, describe how cache-coherency protocols ensure that CPUs agree on t
Introduction: While working with Memcache the other night, it dawned on me that it’s usage as a distributed caching mechanism was really just one of many ways to use it. That there are in fact many alternative usages that one could find for Memcache if they could just realize what Memcache really is at its core – a simple distributed hash-table – is an important point worthy of further discussion. To be clear, when I say “simple”, by no means am I implying that Memcache’s implementation is simple, just that the ideas behind it are such. Think about that for a minute. What else could we use a simple distributed hash-table for, besides caching? How about using it as an alternative to the traditional shard lookup method we used in our Master Index Lookup scalability strategy, discussed previously here.
Introduction: Consistent hashing is one of those ideas that really puts the science in computer science and reminds us why all those really smart people spend years slaving over algorithms. Consistent hashing is "a scheme that provides hash table functionality in a way that the addition or removal of one slot does not significantly change the mapping of keys to slots" and was originally a way of distributing requests among a changing population of web servers. My first reaction to the idea was "wow, that's really smart" and I sadly realized I would never come up with something so elegant. I then immediately saw applications for it everywhere. And consistent hashing is used everywhere: distributed hash tables, overlay networks, P2P, IM, caching, and CDNs. Here's the abstract from the original paper and after the abstract are some links to a few very good articles with accessible explanations of consistent hashing and its applications in the real world. Abstract: We describe a family of caching
6 0.90544468 330 high scalability-2008-05-27-Should Twitter be an All-You-Can-Eat Buffet or a Vending Machine?
7 0.90142596 1466 high scalability-2013-05-29-Amazon: Creating a Customer Utopia One Culture Hack at a Time
8 0.89210153 860 high scalability-2010-07-17-Hot Scalability Links for July 17, 2010
9 0.88934755 778 high scalability-2010-02-15-The Amazing Collective Compute Power of the Ambient Cloud
10 0.8854962 1414 high scalability-2013-03-01-Stuff The Internet Says On Scalability For February 29, 2013
same-blog 11 0.88528746 97 high scalability-2007-09-18-Session management in highly scalable web sites
12 0.87991202 879 high scalability-2010-08-12-Think of Latency as a Pseudo-permanent Network Partition
13 0.87880003 848 high scalability-2010-06-25-Hot Scalability Links for June 25, 2010
14 0.8634063 27 high scalability-2007-07-25-Product: 3 PAR REMOTE COPY
15 0.86046535 757 high scalability-2010-01-04-11 Strategies to Rock Your Startup’s Scalability in 2010
16 0.85792065 1492 high scalability-2013-07-17-How do you create a 100th Monkey software development culture?
17 0.84802788 768 high scalability-2010-02-01-What Will Kill the Cloud?
18 0.81556362 300 high scalability-2008-04-07-Scalr - Open Source Auto-scaling Hosting on Amazon EC2
19 0.79701328 19 high scalability-2007-07-16-Paper: Replication Under Scalable Hashing
20 0.79203981 360 high scalability-2008-08-04-A Bunch of Great Strategies for Using Memcached and MySQL Better Together