Presentación
PDF (pincha para descargar)
Vídeo
Transcripción
Extracto de la transcripción automática del vídeo realizada por YouTube.
hi everyone thanks for picking our session this morning so this is Tigerettes keep your reverse proxy cache up to date and so you've probably seen some of these things from some of these questions from clients when they can't see that their content
is actually updated even though they've actually just made that update so where your session presenters and I'm Christian and it's just a couple little pictures and things of me I live in New York City's theater district and this is me flying
fee fee which is one of the last of its kind in particular kind of aircraft and also hiking on top of the state of Vermont's tallest mountain Mount Mansfield I live in hoboken new jersey which is across the river from manhattan which one of the most fabulous
views of Manhattan I was recently introduced to four wheeling ATVs and had so much fun now I want to learn how to drive a race car and on the lower corner there is my roommate my co-conspirator my partner in crime Harvey the shelter dog and christian and i
are from columbia university one of the world's great universities located in new york city it was founded in 1754 originally called King's College and then we had a little revolution and the school was renamed to Columbia which means new America Columbia
has about 29,000 students 18 schools and boasts the largest number of Nobel laureates of any other university at 82 Christian and I actually worked for the law school Columbia Law School which has expertise in many areas of the law of particular attention
to this group might be our intellectual property faculty and our digital technology law faculty picture it is Professor Tim Wu who some of you may know as having coined the term net neutrality and another member of our faculty who may be familiar to you was
named eben moblin he's been a very dynamic advocate for the open source movement I'll tell a little bit about what we're covering today the complex caching issues that we faced at columbia law school and how we solve them why it's critical
for your site to reflect updated published information as soon as possible current and validation techniques and why they don't always work for all of us as well as developments in building smarter caches and Drupal 8 when i arrived at columbia I was faced
with some challenges as far as web goes we had a legacy system that had more than 10,000 pages of unstructured content to even bring it into some sort of usable site we were looking at about two years worth of development to deliver services that were sorely
overdue the problem was that our legacy system really had no future there was no community there was no more core development being done by the vendor and there was no stakeholder support so we started to look for a new content management system and we had
to establish guiding principles to what it was going to be the first one is that we were looking for an open source solution the solution had to be scalable but also infinitely flexible for the vast number of customizations that we needed to be able to do
and we were looking for something that was supported by a community that was as vibrant and as innovative as our own we discovered Drupal a little bit about our production environment we have about 5,500 authenticated users we have 250 active editors of very
robust public sites we also have about 3,700 total unique visitors during peak periods right now would be one of them for us because we just started school alright so when it comes to our content currently and we're not completely migrated from the legacy
CMS yet anonymous users have access to request so this is just anonymous users we have a lot more content that authenticated users can access but for anonymous users we have about 10,000 entities and roughly half of them are extremely volatile meaning that
we the data change is very often and at times we don't know exactly when it changes we have a lot of editors and you know the central team isn't always able to keep up with them about 4,700 menu links belong to about 115 custom menus use custom menus
to permission out those those menu authorizations to different editors a little more than 11,000 custom path aliases thousand redirects using redirect so these are interactively configured and not in HT access or or encode about 150 contexts right now in we
use context module 120 views not that many where now but we're working up the same thing with taxonomy terms we haven't really converted most of our big article libraries yet and so are our vocabularies in terms in text and taxonomy are pretty low
at this point so our infrastructure when we decided to make this change over we this was actually just before Drupal 7 was released and we decided not to go with Drupal 6 for varying reasons but the thing that we were sort of concerned about with Drupal 7
was with performance and so we decided still to go with Drupal 7 but that we had to definitely do our research and our home work so right now we currently have 190 total enabled modules about 134 for contribute soup for some of the technology that we use to
run the site so when present someone like me I'm not a developer I'm a communications director and I get presented with this and I really have no idea what needs to happen except that we have to fix it so how do we deal with all of this well to quickly
say that we had to take a look at the actual performance implications and so because our team and the school really relies on having content being up to date at all times we have to make sure that we could actually do that so when we looked at performance
in general when we heard that there may be some more concerns with Drupal 7 than Drupal 6 we made sure that we took a look at other peoples other organizations infrastructure so of course one of the things that we added into the mix was reverse proxy cache
serving fortunately it also brings some problems with updated content so let me first just go into how how many of you know that normal page serving works so normally you would have your drupal web app servers probably load balancer in front of that and all
requests are processed directly by those Drupal servers and even for pages that haven't changed of course that's not very performant in this case an editor updates for example an event node and that event node gets processed by drupal and comes back
to it and also a visitor let's say requests that same event page and even though it may have been requested 150 times in that last minute Drupal still processes that request so that's not very performant because the same thing happened over and over
again with the same response of course with reverse proxy caching normally what happens is what we do is we add another tier here we add the reverse proxy cache server which maybe varnish or squid or ingenix and you may even actually look at some work that's
[ ... ]
Nota: se han omitido las otras 3.358 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.