Ok, here’s the deal. We have gone over this here in the office, and thought we would offer it up to you, our trusted Forumvarians for review.
What haven’t we thought of? What issues do you see? Read the following and let us know…
As with past years, in addition to 8,000 4-day passes (which sold-out this year on 12/25) we have set aside 1,500 single-day tickets per day. Those tickets bring us to the 9500 tickets we sell per day for the festival (the remaining tickets are for crew, volunteers, artists, etc...). Based on the phone calls and emails we've been receiving for the past few weeks, we foresee an unprecedented demand for these remaining tickets.
Unfortunately, we can't predict the true scale of this demand. So after investigating immediate improvements to our webserver to handle record traffic, we have determined that our online ticketing site needs a fundamental overhaul to sell high-demand tickets like these. We learned our lesson from from our initial on-sale day, and we do not want to risk any festivarians dealing with the frustrations of page-timeouts and other website problems for hours.
Our solution - which we have employed for our most in-demand tickets for the past few years - is an online lottery. (After all, even with the most robust online ticketing site, you are essentially participating in a real-time lottery when ordering exceptionally high-demand tickets.)
This TBF single-day lottery will be open from Tuesday, Feb 7 at 12:01am MST thru Thurs, Feb 9 at 11:59pm MST at bluegrass.com.
It has been suggested that we give-in to supply and demand and increase the price of these remaining single-day tickets. We will not be doing that, but instead holding single-day tickets to the same price as last year: $65 per day.
Many Festivarians have been expressing concern about scalpers. Unfortunately, we have no way of distinguishing scalpers from Festivarians (either in a lottery or when purchasing phone/online), so we are adding several anti-scalper measures to this lottery:
- Limit of 1 entry per credit card number
- Each entry may request no more than 2 tickets per day
- Tickets are non-refundable
Because many of you are telling us that you are just looking for 4-day passes, the lottery form will allow you to request either:
- up to two 4-day passes ($260 each)
- up to two single-day tickets for each/any/all of Thurs/Fri/Sat/Sun ($65 each)
When we process lottery entries we will fill any tickets on your entry that are still available - e.g. if you requested Fri/Sat/Sun single-day tickets and Fri tix are already sold-out we will sell you Sat/Sun tickets.
If you are only interested in coming all 4 days, you should request 4-day passes; if you would settle for less than all 4 days you should request Thurs/Fri/Sat/Sun single-day tickets (knowing that you may only receive single-day tickets for some of those days).
You may enter anytime on these 3 days with the same chance of being randomly selected. When we begin processing orders, we will randomly sort all entries and begin filling each entry in that randomly assigned order.
Dustin, thank you for putting consideration into the single day tickets and trying to balance various perspectives (as well as for not caving in on bumping up the price).
In case you haven’t looked into it, cloud servers might prove to be effective in allowing you to scale up to the necessary resource level without having to pay for those resources all year when it’s not needed.
I’m sure you are getting plenty of requests for 4-day passes, but my suspicion is there will still be a demand for single day tickets … especially from locals who were used to merchant passes and/or those who are stuck working at least half of the festival and who would like to attend at least a day or two.
Perhaps a similar 5% (or more) allotment of about 75 (to 150) single day tickets per day might help to fill this particular demand. Maybe even require locals to prove residency to get wristbands placed on them at the show such as with Phish. Maybe this is too much of headache at this point.
On a related note: my first thought is that while I see the logic of “equivalency” regarding the either system being a “lottery” of sorts, a bogged down server will probably allow more (different) people to get tickets vs. consolidating them in fewer hands (via “bundling”)… even in light of it being a frustrating process. Maybe the latter is a more manageable situation from PB perspective, but it also maybe cuts against the grain of the single day ticket in so far as it having been historically an opportunity for people who can’t commit to the full weekend to at least zero in on their favorite acts (if finances are tight) or simply attend on the day or two when they’re off work.
I’ve seen a similar sort of system implemented for other multi-day events (I believe SCI Winter Carnival last year had a 3-day option) but it’s almost always implemented as a “workaround” to actually not having a physical multi-day pass and is offered up on the first go around (not after all passes have been sold).
Anyhow, I’ve got my 4-day pass … so there’s nothing in it for me, but maybe if I didn’t have one in hand then I’d be more in favor of bundling single days. Along these lines, it’s possible people who are going to chime in on this are “in it for the weekend” … or to put it another way, it might not be a fair “vote” if you’re tallying remarks from this thread.
Regardless, I think it’s excellent to throw this out there for us to toss around!
Thanks Dustin, I know a lot of thought has gone into this, and in the absence of a perfect solution (which I don’t have), this seems like an improvement. :medal
FOM, I suspect that the PB online store won’t scale on a cloud. Sure, you can put it on something like AWS, but there are various considerations: What dependencies does it have on goofy things that you would need to co-locate, how is it coded, and what is the data store. My gut feel is it was a fine little bit of coding for a mom & Pop operation that isn’t processing a lot of orders, but it seems to have a lot of blocking and locking code in place that leads to the timeouts. It’s not just the server overloading, it’s the architecture not being designed to scale to this level.
I could be wrong, but I’m a geek in real life, and that’s sure how I would diagnose it.
Nice Price. Perhaps offering to merchants that missed out would be cool. Seems like it’s going to be quite the sold out event w/ possibility to attract more daytime acts to the local establishments? Perhaps PB is already working w/ local merchants that have live music venues (outside Bluegrass Pancakes) to create more daytime Music? Certainly Elks Park would be packed if the tickets have gone to Participants and not scalpers. Perhaps speakers at the top of the Hill and a simple loop around Main St. Up/ Dn. @ Aspen St. and Fir St. for the week-end, pedestrian mall feel w/ open container/ Fat Tire dispensary/ Bar on Oak St? Not sure why the tickets are on sale from Mon. @ midnight till Thurs. at noon, figure they’d be gone in a few hours from what we’ve seen this year? Always better Safe than Sorry. :cheers
HF: now you’re talkin’ my language! You may very well be correct about the bottleneck being in the software & throwing more hardware at the issue won’t do any good. Sometimes you don’t realize code is “inefficient” until it’s placed under the gun with a higher load. A migration to a new hosting environment will invariably uncover many instances of the devil being in the details as you’ve alluded to.
One tactic being used by Front Gate Ticketing which I’ve noticed over the past year (which I believe is used to mitigate issues related to software bottlenecks AND perhaps a way to not have to invest in more hardware) is to throttle customers’ access to the actual “shopping area” - where you select tickets, place them in a cart, and then checkout - by allowing in only the number of visitors the system can handle at any given time while simultaneously placing the rest of the line into an ordered que or “waiting room”. So, if for instance 5000 people are looking to buy tickets and the system can only accommodate 2000 visitors within the “shopping area”, then the first 2000 will be allowed in immediately and the remaining 3000 people get assigned a number to “wait in line” to gain entry into the shopping area. Subsequently, for every person who “checks out” another person is let in to the shopping area from the que.
The above solution might be all well and good, but it also might cost $50k to implement. On the other hand, it could very easily be more like a “module” which can work with most any existing system with just minor configuration. I have no idea what’s actually involved, but it might be something to shoot for in subsequent years. Maybe even anticipating a slight increase in the cost of tickets to fund such an improvement … especially if after it’s all said and done this year that it’s deemed there were unintended consequences with respect to policy changes involving the bundling of single day tickets.
Paying a project manager, a couple of developers, a business analyst, and a tester or two for a few months of work would probably cost at least $100k… And that’s if they’re not contractors. Even if there’s a prepackaged solution out there, it’ll probably cost a substantial amount for licensing, and maybe a support contract.
Either way, the lottery is certainly a much cheaper solution.
:flower Fan of the path of least resistance, so long as no one is really hurt. I also, really love how the lottery shall dispense tickets in a bit of random, uncertain way; still those who will make the scene better will be in the scene. :thumbsup
The limitations of the web and shopping cart are a bit out of my area of expertise, but I believe you are generally spot on Huckin. We could look into cloud options, but ultimately it’s a bigger issue with the overall design of our modest little shopping cart. Even if we could get more server space to handle the volume, we are just not currently set up to sell lots of tickets fast. Someone would get a raw deal…likely lots of people.
Face and Iriecycle, tell everyone you know this information. We’ll have something up on the website probably later today, or send them here. Telluride locals should assume that these are the last of the tickets and put into the lottery just like everyone else. As it stands these are the last tickets available for the festival.
Jackalope: I don’t know the answer to that question, but Jasmine certainly will know the possibility of that happening. I’ll get with her and we’ll let you know. It’s a great question, I’m just not sure if it’s humanly possible for her to accept them all that fast. Stand by for an answer.
FOM and HF: Indeed, you’re right on your analysis of our online store. It’s served us relatively well for the steady ticket sales we usually see, but it isn’t designed to handle large spikes very gracefully. Our initial thought was to move to a cloud computing model to give us additional resources for spikes like this, but the software itself just won’t scale very well.
A newly designed online ticketing site is on top of our list for next fall. We’ll certainly be looking at options like a “waiting room” and other enhancements specific to high-demand tickets. Kind of exciting, really. But we’ve got some festivals to focus on before then…
Thanks for everyone’s feedback on this. :thumbsup We’ll continue to watch this thread closely, so keep the comments coming…
To clarify on FOM’s initial questions about single-days vs 4-day passes…
You’ll be able to request single-day tix for any/all days or a “4-day pass” - and the chances of your entry being selected in the lottery are the same.
Our only reason for adding the “bundled” 4-day pass is to give you the option of requesting “4-day pass or nothing.”
The difference between requesting “a pair of single-day tix for each day” vs “4-day pass” is: if we’ve already sold-out of a day when your order is randomly selected (say, Saturday is sold-out), the 4-day pass order would get nothing, but the order that requested a pair of single-days for each day would get Thurs/Fri/Sun tickets (but no Saturday).
I think this is probably as close to a perfect solution as we can get at the moment. Yes, there are probably better options, but none that could be implemented in time for single day sales. Granted, I already have my TP pass, so my opinion may be different from those who are still waiting to get tickets.
Does this mean the FULL line up will be announced by Feb 7th!!! :clap
I think the lottery system is a great option, and probably the best one for a quick-fix such as needed now. But like Hot Sugar, I already have my tix, so perhaps it doesn’t mean much from me either.
We’ll announce as much of the single-day lineup as we can prior to the lottery. At this point I don’t know how much that will be, but we’re pushing hard to have each day’s last 3 artists (and a few others) ready to announce by then…