BEGIN:VCALENDAR
PRODID: 1
VERSION:2.0
METHOD:PUBLISH
X-WR-TIMEZONE: America/Los_Angeles
DTSTAMP: 20240328T194828
BEGIN:VEVENT
UID: info@vconferenceonline.com
SUMMARY:Are Spiders Eating Your Servers? The Impact of Their Unexpected Load and How to Counter It
PRIORITY:0
CATEGORIES:SESSION
CLASS:PUBLIC
DTSTART:20170502T110000
DTEND:20170502T120000
URL: https://event.vconferenceonline.com
DESCRIPTION:For years I've watched people try to tame \"database problems\" with a focus on their code, their SQL, their app server, and so on. Yet often it turns out that the root cause is actually unexpected load. And that load may be from things you never expected (automated), at volumes you never expected. I've found folks with as much as 80% of their web traffic to be such unexpected automated traffic! Worse, there are characteristics of such automated visits that may actually have MORE IMPACT than \"real users\".\n\nA common reaction on learning of this unexpected volume is to want to \"block\" such automated requests, and perhaps some could be, but most just needs to be better \"managed\". (And bad guys have become clever about looking like \"regular users\".) The good news is that there are solutions to better manage (or simply block) such automated requests which may already exist in your environment, and there are tools you may consider (some free, some commercial) which can be easily implemented. There are even SAAS solutions which could help alleviate such problems with just a single tiny change in your environment!\n \nIn this session, veteran server troubleshooter Charlie Arehart will guide a detailed review of the issue, including how to identify such traffic, more on their specific impact, and most important identifying the solutions along with their pros and cons. He has helped shops achieve dramatic reductions in impact from such automated requests, resulting in greater server stability and performance."}" style="font-size:13px;font-family:arial,sans,sans-serif;">For years I've watched people try to tame "database problems" with a focus on their code, their SQL, their app server, and so on. Yet often it turns out that the root cause is actually unexpected load. And that load may be from things you never expected (automated), at volumes you never expected. I've found folks with as much as 80% of their web traffic to be such unexpected automated traffic! Worse, there are characteristics of such automated visits that may actually have MORE IMPACT than "real users".
A common reaction on learning of this unexpected volume is to want to "block" such automated requests, and perhaps some could be, but most just needs to be better "managed". (And bad guys have become clever about looking like "regular users".) The good news is that there are solutions to better manage (or simply block) such automated requests which may already exist in your environment, and there are tools you may consider (some free, some commercial) which can be easily implemented. There are even SAAS solutions which could help alleviate such problems with just a single tiny change in your environment!
In this session, veteran server troubleshooter Charlie Arehart will guide a detailed review of the issue, including how to identify such traffic, more on their specific impact, and most important identifying the solutions along with their pros and cons. He has helped shops achieve dramatic reductions in impact from such automated requests, resulting in greater server stability and performance.
LOCATION:
END:VEVENT
END:VCALENDAR