Techno issues: servers, connections, refresh, etc
I am not a technology expert, but have worked on web sites and projects over the last 10 years or so. I have good friends who are programmers (one programed the original "JamBase") both of whom are 10c members and familiar with the system and problems. I read the various posts and threads on problems with the site, and chatted with these guys last night. I am throwing the following out for discussion, and apologize in advance if anything is factually incorrect.
1. Connecting through the secure page rather than through frames:
Connecting directly through https://secure.pearljam.com/store/produ ... tegoryId=3 rather than http://www.pearljam.com is essential. Connecting through the main site requires the secure connection to load in a frame, which takes time which is precious.
2. Do not hit "refresh":
When you have a secure connection, nothing can be stored in your cache. Thus, hitting "refresh" makes all the content re-load into cache. While there are few images (the ticket images, the button mouse-overs), this does require more time, which is precious.
3. Instead, click "tickets":
Clicking on a link to a page within the secure connection (instead of refreshing) is a request within the connection, rather than a new request for a connection. Once you have a secure connection, the trick is to keep it alive. There is a "keepalive" setting on the server, which allows you to keep your connection for a re-specified amount of time (e.g., in the range of 30-60 seconds - I have no idea what 10c server is set to). As long as you perform an action within this window, you should keep your connection alive.
4. Speed kills:
While it may not be the lone factor, having a fast connection is better than a slow connection. DSL and cable modems connect at about 25 Mbps download and about 3 Mbps upload. Using http://www.speedtest.com (click "start test to recommended server" - no software dl required) my home DSL (0% success) vs connection a work (near 100% success) clocked in at:
13.0 down/2.9 up (wireless to modem)
19.9 down/2.7 up (ethernet to modem)
78.5 down/23 up (T1 or T3 line)
While the "packet" request associated with a "buy" or "continue" button is quite small, I would rather be 10x faster than the other guy. Even though we are both connected, speed saves time, which is precious.
5. The connection-to-request ratio is quite low.
Keep in mind, there are thousands of people competing for a finite number of connections and ticket pairs. Anything you can do to connect, keep connected, and get your request in ASAP will be in your benefit. However, there is luck and timing involved, some of which is beyond your control.
6. One possible solution:
Cloud computing (http://en.wikipedia.org/wiki/Cloud_computing) is a relatively new technology that allows multiple servers to share the load. There are disadvantages and benefits... among the problems is that your database is hosted on multiple servers... while my database-fu is weak, it is always better to own and control a single server/box. On the upside, cost is low (see http://www.rackspacecloud.com/?CMP=rackspace). However, while this would relieve the server strain and connection problems, tickets would be gone even faster.
Hope this generates helpful dialog, and no offense intended if I took any liberties.
1. Connecting through the secure page rather than through frames:
Connecting directly through https://secure.pearljam.com/store/produ ... tegoryId=3 rather than http://www.pearljam.com is essential. Connecting through the main site requires the secure connection to load in a frame, which takes time which is precious.
2. Do not hit "refresh":
When you have a secure connection, nothing can be stored in your cache. Thus, hitting "refresh" makes all the content re-load into cache. While there are few images (the ticket images, the button mouse-overs), this does require more time, which is precious.
3. Instead, click "tickets":
Clicking on a link to a page within the secure connection (instead of refreshing) is a request within the connection, rather than a new request for a connection. Once you have a secure connection, the trick is to keep it alive. There is a "keepalive" setting on the server, which allows you to keep your connection for a re-specified amount of time (e.g., in the range of 30-60 seconds - I have no idea what 10c server is set to). As long as you perform an action within this window, you should keep your connection alive.
4. Speed kills:
While it may not be the lone factor, having a fast connection is better than a slow connection. DSL and cable modems connect at about 25 Mbps download and about 3 Mbps upload. Using http://www.speedtest.com (click "start test to recommended server" - no software dl required) my home DSL (0% success) vs connection a work (near 100% success) clocked in at:
13.0 down/2.9 up (wireless to modem)
19.9 down/2.7 up (ethernet to modem)
78.5 down/23 up (T1 or T3 line)
While the "packet" request associated with a "buy" or "continue" button is quite small, I would rather be 10x faster than the other guy. Even though we are both connected, speed saves time, which is precious.
5. The connection-to-request ratio is quite low.
Keep in mind, there are thousands of people competing for a finite number of connections and ticket pairs. Anything you can do to connect, keep connected, and get your request in ASAP will be in your benefit. However, there is luck and timing involved, some of which is beyond your control.
6. One possible solution:
Cloud computing (http://en.wikipedia.org/wiki/Cloud_computing) is a relatively new technology that allows multiple servers to share the load. There are disadvantages and benefits... among the problems is that your database is hosted on multiple servers... while my database-fu is weak, it is always better to own and control a single server/box. On the upside, cost is low (see http://www.rackspacecloud.com/?CMP=rackspace). However, while this would relieve the server strain and connection problems, tickets would be gone even faster.
Hope this generates helpful dialog, and no offense intended if I took any liberties.
37 PJ Shows, 3 EV Shows, 1134 Total Songs, 24 Different Openers, 9 Different Closers, 252 Unique Songs (never enough)
0