Quarantined Conferences: Claustrophobic Technophiles or Attentive Audiences?

Loren Feldman. 1938 Media. Audience Conference.

That’s about as much of a summary as you’ll find about the Audience Conference held in New York last Friday. That’s because there were no open laptops allowed during the performances. There was also no Wi-Fi, no video streaming, no tweeting, and no blogging. Something akin to omertà joined the members of the Audience Conference together.

This bond of silence was at the core of the Audience Conference, and it goes against everything that technology and Web 2.0 events normally stand for: openness, transparency, and participation. You would be hard-pressed to find any information anywhere on the web about any of the Audience Conference content. Tweets during the event were generic (“just arrived at the Audience Conference”) and posts after the event were vague (“loved the conference, got to meet Calacanis”). Nobody knows what happened unless you were a genuine member of the audience.

Many other features of the event were also unfamiliar. There were no sponsor booths, banners, and signs all over the place, the speakers had no slideshows, internet connections, or videos to keep us interested, and there were no press or even questions from the audience allowed. No problem.

That’s because the content and experience was so damn good. It was technology. It was performance. It was even culinary. Loren Feldman, our MC for the day, treated the event not as a conference so much as a 20-act play that he directed from start to finish. Inside the historic Hudson Theatre in New York, the members of the audience acted like precisely that - an audience. We watched, listened, and learned. We didn’t talk, text, or tweet. We sat in comfortable chairs facing the stage, not at round tables facing at all different angles to it. We retained the information we heard instead of regurgitating it for our own audiences. We learned that the essence of having an audience is performing for them on a stage - perhaps a digital one - and telling great stories.

What was the Audience Conference? From the website: "Audience is a conference aimed at those who recognize the need to reach engage and influence audiences of all kinds, an investigation into how this is changing, and a look at how technology has in the past and is now, through new media tools and the social web, changing audience participation and interaction." I would love to tell you about what I learned from Jason Calacanis and Rachel Marsden and Rae Hoffman and Andrew Keen and Jeremy Schoemaker and Joe Jaffe and Melanie Notkin and others. But I won’t. Half the philosophy of the Audience Conference was that events are ephemeral experiences that people attending can share with each other - and people not there cannot experience.

In my opinion, casually live-tweeting conferences is overrated because to a large degree it doesn’t serve an external audience very well. When 30 people are tweeting 10 times during each of 10 talks at a conference, and then people re-tweet the tweets (on a delay, naturally), the hashtag stream is a jumbled mess of disjointed quotations that don’t tell a coherent story. I’ve written about why I think tools like Posterous might be better for summarizing thoughts from events; they serve the audience better.

That said, I disagree with the notion that everything needs to be live streamed, live blogged, and live tweeted merely because we can. I recently attended a conference that was about the size of the Audience Conference, and I had a fine experience there so there’s no need to call them out. But strange to me in hindsight was that the audience’s tables were arranged at 90 degrees to the stage, and furthermore that nearly everybody at the tables was staring into a laptop nearly the entire event. Who is that a great experience for?

Now, I am not going to start calling for a ban on Twitter at conferences. I do it sometimes when I think it provides unique value and perspective. I’ve live-blogged some events myself. Furthermore, banning these technologies at an event like the upcoming Gov 2.0 Expo would probably result in an all-out revolt. But what Audience Conference taught me was a new perspective on the actual value that all of the technology adds; if you’re planning an event and you’re more worried about power strips and Wi-Fi than content and experience, you’ve got a problem in my opinion.

The comments on Nicole Ferraro’s blog about Audience Conference might lead you to believe that being able to film and tweet from a private, closed door event was some God-given right of Those Who Possess An iPhone. Sorry, it’s not. Loren Feldman took video of the entire event from six different angles (including a small cam pointed at, you guessed it, the audience) and he will decide how and what and when you get to see anything. Why not? It’s his show, not yours. Can you stream video from a live production of Wicked?

The other half of the philosophy of the Audience Conference was that it’s okay that people are better than you at something. And it’s perfectly alright to just sit back and watch them perform. And we watched performances, to be sure - not just tech talks but also personal stories, poetry readings, and musical acts. (Yeah, musical acts.) Not everyone is good enough to be the best financial blogger, or best personality, or best musical act - that’s a dream. Maybe you’re great at something, but can’t you sit back and relax the rest of the time?

I liked this too. With all the talk about how everyone is a citizen journalist and everyone is a content producer and everyone needs a digital media strategy it’s easy to forget that most people are horrible at all of this stuff. And that’s not necessarily because people don’t understand whatever shiny object has come along, it’s because many people are not gifted communicators. New media, at its core, is old-fashioned because the instinct to communicate with other individuals predates man. But some are way better than others at it. And that’s okay.

So are quarantined conferences more likely to result in claustrophobic technophiles or attentive audiences? While some in the tech community clearly think that a lack of engagement is a violation of some imaginary social media code and in an age where even live music isn’t sacred it may seem like heresy to sequester people participating in your event away from their new media toolbox. And maybe sometimes it is. But having experienced the Audience Conference myself, I can also say that in some situations people are not entitled to break out the social media toolbox, because they will genuinely gain a more valuable experience without it. In my opinion, if one event wants to encourage new media use and another discourages it, who are we to argue? We’re only the audience.

What do you think? Were people at the Audience Conference correct to obey Loren Feldman’s requests? Should they deliberately continue “hiding” the content of the event from people that chose not to attend? Should other Web 2.0 events disallow Web 2.0 usage in real time??

.

Four short links: 28 October 2009

Great Mail Feature, Speed Talks, Virtualisation History, Science Literacy

1. GMail Labs: Got The Wrong Bob? -- When's the last time you got an email from a stranger asking, "Are you sure you meant to send this to me?" and promptly realized that you didn't? Looks at the clusters of CCs you send and, if you normally send to Bob X but are trying to send it to Bob Y, asks you "did you mean Bob X?". This might be the best thing to happen to email since webmail and full-text search--it's ridiculous how little innovation is happening in email given how widely and heavily it is used.
2. Speedgeeks LA at Shopzilla -- eight talks about making websites faster. Latency Improvements for PicasaWeb - Gavin Doughtie (Google) - Great tips from a web guru about what makes PicasaWeb fast. Watch for when the slides to more talks become available.
3. 10 Years of Virtual Machine Performance Semi-Demystified -- fascinating history of virtualisation from someone who worked for VMware. Since 2005, VMware and Xen have gradually reduced the performance overheads of virtualization, aided by the Moore’s law doubling in transistor count, which inexorably shrinks overheads over time. AMD’s Rapid Virtualization Indexing (RVI - 2007) and Intel’s Extended Page Tables (EPT - 2009) substantially improved performance for a class of recalcitrant workloads by offloading the mapping of machine-level pages to Guest OS “physical” memory pages, from software to silicon. In the case of operations that stress the MMU—like an Apache compile with lots of short lived processes and intensive memory access—performance doubled with RVI/EPT. (Xen showed similar challenges prior to RVI/EPT on compilation benchmarks.)
4. Pew Research Science Quiz -- To test your knowledge of scientific concepts and recent scientific findings and events, we invite you to take this 12-question science knowledge quiz. Then see how you did in comparison with the 1,005 randomly sampled adults asked the same questions.

More on how web performance impacts revenue...

At Velocity this year Microsoft, Google and Shopzilla each presented data on how web performance directly impacts revenue.

Their data showed that slow sites get fewer search queries per user, less revenue per visitor, fewer clicks, fewer searches, and lower search engine rankings. They found that in some cases even after site performance was improved users continued to interact as if it was slow. Bad experiences have a lasting influence on customer behavior.

What about smaller websites that aren't yet at this scale?

Alistair Croll and Sean Power, the authors of the new book Complete Web Monitoring, have continued this research for sites at smaller scale.

They used a Strangeloop Networks web acceleration appliance to optimize half the sessions to a smaller production website, tagging optimized and unoptimized visitors so they could be analyzed in Google Analytics. The Strangeloop device applies many of Steve Souders' performance rules to an existing site automatically (a kind of "Steve-in-a-Box" ;-).

The results of their analysis show how significant a reduction in page latency can be. In addition to reducing bounce rates, and increasing pages per visit & time on site, they found a 16.07% increase in conversion rates and a 5.50% increase in average order value.

Check out the full post on the Watching Websites blog.

John Adams on Fixing Twitter: Improving the Performance and Scalability of the World's Most Popular Micro-blogging Site

Twitter is suffering outages today as they fend off a Denial of Service attack, and so I thought it would be helpful to post John Adams’ exceptional Velocity session about Operations at Twitter.

Good luck today John & team… I know it’s going to be a long day!

Update: Apparently Facebook & Livejournal have had similar attacks today. Rich Miller from Data Center Knowledge reminds us that this is just the latest in a series of major attacks.

Four short links: 1 July 2009

Web Awards, Speed Thrills, Magazines in the Cloud, Augmented Reality

1. The Onyas -- New Zealand web design awards launch, from the people behind Webstock and Full Code Press. The name comes from "good on ya", the highest praise that traditionally taciturn New Zealanders are allowed by law to give.
2. The Year of Business Metrics: Don't make your users run away! -- wrapup of the Velocity conference. AOL: Users who had a slower experience view far fewer pages. Some interesting notes on performance from a Google-Bing study: Notice that as the delays get longer the Time To Click increases at a more extreme rate (1000ms increases by 1900ms). The theory is that the user gets distracted and unengaged in the page. In other words, they've lost the user's full attention and have to get it back. [...] As much as five weeks later, some users, especially those who saw delays greater than 400MS, were still searching less than before. (via timoreilly on Twitter)
3. Printcasting -- very simple content management system for print magazines that lets anyone start a magazine, add content, sign up contributors, sell ads, and go. Clever!
4. Pachube Augmented Reality Hack -- sexy hack that pushes all my buttons: computer vision, Arduino, sensor network, ubiquitous computing, pervasive alternate reality cyborg villians with chalk designs hellbent on world domination and the enslavement of the human race to use as meatsack AA batteries for their sex toys. Okay, four out of five ain't bad. (via bruces on Twitter)

Four short links: 29 June 2009

Syadmin Wiki, Physics, National Archives, and Reinventing the British Government

1. Server Fault -- Wikipedia-like sysadmin guide, built by the Stack Overflow team, who are branching out to reach a more general IT Professional audience. (via Brady in email)
2. Sixty Symbols -- 5m videos about the symbols of physics and astronomy. Great stuff! (via Glutnix on Twitter)
3. US National Archives launches YouTube Channel -- a mixture of archives-nerd stuff (directors of Presidential Libraries talking about their favourite items) and wider-interest collections (such as Touring 1930s America).
4. Open House in Westminster -- the ever-insightful Tom Steinberg from MySociety has an article in the Independent about British plans to reinvent government. Now the talk of Westminster is all about democratic reform. By my count there are over 50 different ideas for changing the way our democracy works being touted by different pundits at the moment. [...] What all these ideas, though, have in common is that they propose structural reforms that could have been achieved any time in the last 200 years.[...] My view is that these proposals are all interesting, and some may be quite critical for a better democracy. But I am also concerned that they do not see Parliament and the process of making laws as a native to the internet would. They don’t ask: “What reforms are possible that just weren’t conceivable ten years ago?”

Jonathan Heiliger on Web Performance, Operations, and Culture

We were honored to have Jonathan Heiliger, Facebook’s VP of Technology Operations, as our opening keynote speaker at Velocity. Jonathan is one of the most accomplished leaders in our field, and is a master of the craft.

Here is his keynote in its entirety:

Note: Other videos from Velocity are being posted to VelocityConference.blip.tv

Announcing: Spike Night at Velocity

Guest blogger Scott Ruthfield is a Program Committee member of the O'Reilly Velocity: Web Performance & Operations Conference. 

Four short links: 25 Feb 2009

Amazon, Apple, Science, and Databases:

1. Amazon's Wheel of Growth -- a fascinating diagram in the middle, the flywheel of customer experience driving sales driving sellers driving selection which drives experience again, and all the while lower costs allows Amazon to deliver lower prices and thus lower selection.
2. iPhone Sketch -- stencils to use when sketching your iPhone app's screens.
3. The Importance of Stupidity in Scientific Research -- thoughts on the value of feeling stupid ("I actively seek out new opportunities to feel stupid") and how PhD programs don't prepare students for that feeling. "Science involves confronting our `absolute stupidity'. That kind of stupidity is an existential fact, inherent in our efforts to push our way into the unknown. Preliminary and thesis exams have the right idea when the faculty committee pushes until the student starts getting the answers wrong or gives up and says, `I don't know'." (via Titine's delicious stream)
4. First Key-Value Storage Meeting Held in Japan -- yet more work being done with modernized DBM technology. As Joshua said in his delicious comment, plenty of systems I've never heard of before. (via Joshua's delicious stream)

Data Center Power Efficiency

James Hamilton is one of the smartest and most accomplished engineers I know. He now leads Microsoft's Data Center Futures Team, and has been pushing the opportunities in data center efficiency and internet scale services both inside & outside Microsoft. His most recent post explores misconceptions about the Cost of Power in Large-Scale Data Centers:

I’m not sure how many times I’ve read or been told that power is the number one cost in a modern mega-data center, but it has been a frequent refrain. And, like many stories that get told and retold, there is an element of truth to the it. Power is absolutely the fastest growing operational costs of a high-scale service. Except for server hardware costs, power and costs functionally related to power usually do dominate.

However, it turns out that power alone itself isn’t anywhere close to the most significant a cost. Let’s look at this more deeply. If you amortize power distribution and cooling systems infrastructure over 15 years and amortize server costs over 3 years, you can get a fair comparative picture of how server costs compare to infrastructure (power distribution and cooling). But how to compare the capital costs of server, and power and cooling infrastructure with that monthly bill for power?

The approach I took is to convert everything into a monthly charge. [...]

Velocity 2009: Themes, ideas, and call for participation...

Last year's Velocity conference was an incredible success. We expected around 400 people and we ended up maxing out the facility with over 600. This year we're moving the conference to a bigger space and extending it to 3 days to accommodate workshops and longer sessions. Velocity 2009 will be on June 22-24th, 2009 at the Fairmont Hotel in San Jose, CA.

This year's conference will be especially important. I've said many times that Web Performance and Operations is critical to the success of every company that depends on the web. In the current economic situation, it's becoming a matter of survival. The competitive advantage comes from the ability to do two things:

1. Generate more revenue with fewer resources
2. Respond quickly to change

I'm excited to announce that joining Steve Souders & I on this year's program committee are John Allspaw, Artur Bergman, Scott Ruthfield, Eric Schurman, and Mandi Walls.  We've already started working on the program, and have just opened the Call for Participation.

(continue reading)

Incredible images of the Sun

[link courtesy Barry Brumitt]

Two new open source projects at Velocity

At Velocity next week there will be two significant open source projects debuting. The first is the Jiffy: Open Source Performance Measurement and Instrumentation tool created by Scott Ruthfield and his team at Whitepages.com.

Most tools for measuring web performance come in two flavors:

• Developer-installed tools (Firebug, Fiddler, etc.) that allow individuals to closely trace single sessions


• Third-party performance monitoring systems (Gomez, Keynote, etc.) that will hit your site occasionally and report back component-level metrics (for a fee)

Neither of these tools give you real-world information on what’s actually happening with your clients—how long are pages really taking to load, what’s the real cost of client-side execution, and what’s the impact of your loading or dependency chain. This is even more important when you don’t host all of your own assets, such as when you load ads or JavaScript from third parties, for example, and you need to monitor their performance.

Thus we built Jiffy—an end-to-end system for instrumenting your web pages, capturing client-side timings for any event that you determine, and storing and reporting on those timings. You run Jiffy yourself, so you aren’t dependent on the performance characteristics, inflexibility, or costs of third-party hosted services.

The second is project is EUCALYPTUS, the Elastic Utility Computing Architecture for Linking Your Programs To Useful Systems, presented by Rich Wolski from UCSB. This project has already started getting attention. (Many thanks to Surj Patel of Structure08/GigaOM for connecting us!)

Eucalyptus is an open-source software infrastructure for implementing "cloud computing" on clusters. The current interface to EUCALYPTUS is compatible with Amazon's EC2 interface, but the infrastructure is designed to support multiple client-side interfaces. EUCALYPTUS is implemented using commonly-available Linux tools and basic Web-service technologies making it easy to install and maintain.

The talk will focus on the design, the implementation tradeoffs we have identified in implementing Eucalyptus as an exploratory tool, and the ways in which we have chosen to address these tradeoffs in the first version of the software.

CloudCamp gathering after Velocity

On Tuesday after Velocity closes there will be a CloudCamp gathering at Microsoft's San Francisco Office. I'll be going (unless I'm too exhausted to stand).

CloudCamp was formed in order to provide a common ground for the introduction and advancement of cloud computing

Through a series of local cloudcamp events, attendees can exchange ideas, knowledge and information in a creative and supporting environment, advancing the current state of cloud computing and related technologies. As an informal, member-supported gathering, we rely entirely on volunteers to help with meeting content, speakers, meeting locations, equipment and membership recruitment. We also have corporate sponsors that provide financial assistance with venues, software, books, discounts, and other valuable donations. To become a member, simply register for an upcoming event. Anyone may attend a meeting, there are no fees or dues.

It looks like there is now a London CloudCamp being planned for July 16th as well.

(PS: If you still haven't registered for Velocity and want to attend, you can use my 20% discount code "vel08js".)

Maker Faire mimesis and open speculation

O'Reilly's Make magazine and the Maker Faire that we're hosting today and tomorrow in San Mateo, California have been described in many ways, ranging from a revival of the mid-20th-century love for Popular Mechanics magazine to an exciting new impetus for teaching children about science. During my six hours there today, I noted its strong connections to powerful and fundamental human urges toward creation, mastery, and the reproduction of our own culture.

Some of the Maker Faire centers are devoted to the kind of do-it-yourself projects shown in our magazine. Anyone from a four-year-old to a mechanically adept adult can find challenge and satisfaction at these tables. Projects in another building took a big step up, showcasing the brain children of engineers who devoted their spare time to building games and toys or aiding their communities with research projects. A number of the booths seemed to be run by Renaissance men and women who were making a living from their creative combinations of art and technology.

(continue reading)

Velocity preview at Web2.0 Expo

At the Web2.0 Expo this month we have a small preview of some of the topics and speakers at the Velocity Web Performance & Operations conference.  (Radar readers get a 20% discount by using "vel08js" as a discount code... and yes it works with the $300 early registration discount!).

Failure Happens
Friday @ 11:00 am, Room 2009

Artur Bergman and I will kick off the day with an entertaining/informative/eye-opening review of the year’s biggest failures, disasters, and painful lessons learned.

We'll review incidents by underlying root cause with a focus on what could have been done to prevent it. We promise not to be too harsh on anybody, although we will give special attention to particularly ironic failures or those that are "entertainingly coupled" to absurd marketing claims.

(Hint: Send your boss to this talk if they don't understand why you and your whole team need to go to Velocity.)

Even Faster Web Sites
Friday @ 1:30 pm, Room 2012

Steve Souders is the co-chair of Velocity and author of the bestselling book High Performance Web Sites. At the Expo last year Steve gave an incredibly popular talk on the 14 best practices he developed while working as the Chief Performance Yahoo!.

(continue reading)

Steve Souders asks: "How green is your web page?"

Steve Souders, my Velocity conference Co-Chair and author of High Performance Websites, gave me permission to repost this great analysis:

How green is your web page?

Writing faster web pages is great for your users, which in turn is great for you and your company. But it’s better for everyone else on the planet, too.

Intrigued by an article on Radar about co2stats.com, I looked at my web performance best practices from the perspective of power consumption and CO2 emissions. YSlow grades web pages according to how well they follow these best practices. What if it could convert those grades into kilowatt-hours and pounds of CO2?

Let’s look at one performance rule on one site. Wikipedia is one of the top ten sites in the world (#9 according to Alexa). I love Wikipedia. I use it almost every day. Unfortunately, it has thirteen images in the front page that don’t have a far future Expires header (Rule 3). Every time someone revisits this page the browser has to make thirteen HTTP requests to the Wikipedia server to check if these images are still usable, even though these images haven’t changed in over seven months on average. A better way to handle this would be for Wikipedia to put a version number in the image’s URL and change the version number whenever the image changes. Doing this would allow them to tell the browser to cache the image for a year or more (using a far future Expires or Cache-Control header). Not only would this make the page load faster, it would also help the environment. Let’s try to estimate how much.

• Let’s assume Wikipedia does 100 million page views/day. (I’ve seen estimates that are over 200 million/day.)
• Assume 80% of those page views are done with a primed cache (based on Yahoo!’s browser cache statistics). We’re down to 80M page views/day.
• Assume 10%, no, 5% of those are for the home page. We’re down to 4M page views/day for the home page with a primed cache. Each of those contains 13 HTTP requests to validate the images, for a total of 52M image validation requests/day.
• Assume one web server can handle 100 of these requests/second, or 8.6M requests/day. That’s six web servers running full tilt year-round to handle this traffic.
• Assume a fully loaded server uses 100W. Six servers, year-round, consume 5,000 kilowatt-hours per year or approximately 500-1000 pounds of CO2 emissions.

I think this is a conservative estimate, but there are a lot of assumptions above. And six servers doesn’t sound like a lot. 5,000 kilowatt-hours is a drop in the bucket if you look at data center power consumption. But this was just one rule on one page on one site. Think about the impact of not gzipping, not minifying JavaScript, wasteful redirects, and bloated images. If we extrapolate this across all the performance rules across all sites the numbers are much bigger.

Make your pages faster. It’s good for your users, good for you, and good for Mother Earth.

-Steve

Steve has a SXSW Bookreading on Saturday @11 AM, and will be at the O'Reilly booth on Sunday from 3:30-4:30. Stop by and say hello!