high_scalability high_scalability-2011 high_scalability-2011-995 knowledge-graph by maker-knowledge-mining
Source: html
Introduction: MySQL Expert Ronald Bradford explains how one key way to improve the scalability of a MySQL server, and undoubtedly nearly every other server, is to eliminate unnecessary SQL , saying the most efficient way to improve an SQL statement is to eliminate it : The MySQL kernel can only physically process a certain number of SQL statements for a given time period (e.g. per second). Regardless of the type of machine you have, there is a physical limit. If you eliminate SQL statements that are unwarranted and unnecessary, you automatically enable more important SQL statements to run. There are numerous other downstream affects, however this is the simple math. To run more SQL, reduce the number of SQL you need to run. Ronald shows how to use mk-query-digest to look at query execution times and determine which ones can be profitably whacked. Related Articles Quora: What are the best methods for optimizing PHP/MySQL code for speed without caching?
sentIndex sentText sentNum sentScore
1 Regardless of the type of machine you have, there is a physical limit. [sent-4, score-0.171]
2 If you eliminate SQL statements that are unwarranted and unnecessary, you automatically enable more important SQL statements to run. [sent-5, score-1.43]
3 There are numerous other downstream affects, however this is the simple math. [sent-6, score-0.348]
4 To run more SQL, reduce the number of SQL you need to run. [sent-7, score-0.137]
5 Ronald shows how to use mk-query-digest to look at query execution times and determine which ones can be profitably whacked. [sent-8, score-0.556]
6 Related Articles Quora: What are the best methods for optimizing PHP/MySQL code for speed without caching? [sent-9, score-0.254]
wordName wordTfidf (topN-words)
[('statements', 0.422), ('sql', 0.409), ('unnecessary', 0.243), ('articlesquora', 0.204), ('unwarranted', 0.204), ('ronald', 0.183), ('eliminate', 0.178), ('undoubtedly', 0.176), ('affects', 0.17), ('bradford', 0.17), ('profitably', 0.166), ('digest', 0.166), ('downstream', 0.141), ('numerous', 0.137), ('physically', 0.134), ('mysql', 0.133), ('improve', 0.123), ('statement', 0.117), ('expert', 0.113), ('methods', 0.102), ('kernel', 0.101), ('optimizing', 0.097), ('regardless', 0.095), ('explains', 0.094), ('period', 0.093), ('ones', 0.089), ('determine', 0.088), ('saying', 0.086), ('execution', 0.084), ('enable', 0.083), ('nearly', 0.076), ('number', 0.075), ('certain', 0.074), ('automatically', 0.072), ('shows', 0.071), ('however', 0.07), ('efficient', 0.065), ('physical', 0.062), ('reduce', 0.062), ('type', 0.061), ('way', 0.061), ('given', 0.059), ('query', 0.058), ('related', 0.057), ('speed', 0.055), ('server', 0.054), ('important', 0.049), ('machine', 0.048), ('second', 0.047), ('caching', 0.047)]
simIndex simValue blogId blogTitle
same-blog 1 1.0000001 995 high scalability-2011-02-24-Strategy: Eliminate Unnecessary SQL
Introduction: MySQL Expert Ronald Bradford explains how one key way to improve the scalability of a MySQL server, and undoubtedly nearly every other server, is to eliminate unnecessary SQL , saying the most efficient way to improve an SQL statement is to eliminate it : The MySQL kernel can only physically process a certain number of SQL statements for a given time period (e.g. per second). Regardless of the type of machine you have, there is a physical limit. If you eliminate SQL statements that are unwarranted and unnecessary, you automatically enable more important SQL statements to run. There are numerous other downstream affects, however this is the simple math. To run more SQL, reduce the number of SQL you need to run. Ronald shows how to use mk-query-digest to look at query execution times and determine which ones can be profitably whacked. Related Articles Quora: What are the best methods for optimizing PHP/MySQL code for speed without caching?
2 0.15403517 410 high scalability-2008-10-13-SQL Server 2008 Database Performance and Scalability
Introduction: Microsoft SQL Server 2008 incorporates the tools and technologies that are necessary to implement relational databases, reporting systems, and data warehouses of enterprise scale, and provides optimal performance and responsiveness. With SQL Server 2008, you can take advantage of the latest hardware technologies while scaling up your servers to support server consolidation. SQL Server 2008 also enables you to scale out your largest data solutions. This white paper describes the performance and scalability capabilities of Microsoft速 SQL Server速 2008 and explains how you can use these capabilities to: * Optimize performance for any size of database with the tools and features that are available for the database engine, analysis services, reporting services, and integration services. * Scale up your servers to take full advantage of new hardware capabilities. * Scale out your database environment to optimize responsiveness and to move your data
3 0.13758603 961 high scalability-2010-12-21-SQL + NoSQL = Yes !
Introduction: This is a guest post by Frédéric Faure (architect at Ysance ), you can follow him on twitter . Data storage has always been one of the most difficult problems to address, especially as the quantity of stored data is constantly increasing. This is not simply due to the growing numbers of people regularly using the Internet, particularly with all the social networks, games and gizmos now available. Companies are also amassing more and more meticulous information relevant to their business, in order to optimize productivity and ROI (Return On Investment). I find the positioning of SQL and NoSQL (Not Only SQL) as opposites rather a shame: it’s true that the marketing wave of NoSQL has enabled the renewed promotion of a system that’s been around for quite a while, but which was only rarely considered in most cases, as after all, everything could be fitted into the « good old SQL model ». The reverse trend of wanting to make everything fit the NoSQL model is not very p
4 0.13547845 1032 high scalability-2011-05-02-Stack Overflow Makes Slow Pages 100x Faster by Simple SQL Tuning
Introduction: The most common complaint against NoSQL is that if you know how to write good SQL queries then SQL works fine. If SQL is slow you can always tune it and make it faster. A great example of this incremental improvement process was written up by StackExchange's Sam Saffron, in A day in the life of a slow page at Stack Overflow , where he shows through profiling and SQL tuning it was possible to reduce page load times from 630ms to 40ms for some pages and for other pages the improvement was 100x. Sam provides a lot of wonderful detail of his tuning process, how it works, the thought process, the tools used, and the tradeoffs involved. Here's a short summary of the steps: Using their mini-profiler it was shown that a badge detail page was taking 630.3 ms to load, 298.1 ms of that was spent on SQL queries, and then the tool listed the SQL queries for the page and how long each took. From the historical logs, which are stored in HAProxy on a month-by-month basis, Sam was able t
5 0.12967533 63 high scalability-2007-08-09-Lots of questions for high scalability - high availability
Introduction: Hey, I do have a website that I would like to scale. Right now we have 10 servers but this does not scale well. I know how to deal with my apache web servers but have problems with sql servers. I would like to use the "scale out" system and add servers when we need. We have over 100Gb of data for mysql and we tried to have around 20G per server. It works well except that if a server goes down then 1/5 of the user can't access the website. We could use replication but we would need to at least double sql servers to replicate each server. And maybe in the future it's not gonna be enough we would need maybe 3 slaves per master ... well I don't really like this idea. I would prefer to have 8 servers that all deal with data from the 5 servers we have right now and then we could add new servers when we need. I looked at NFS but that does not seem to be a good idea for SQL servers ? Can you confirm?
7 0.11009251 867 high scalability-2010-07-27-YeSQL: An Overview of the Various Query Semantics in the Post Only-SQL World
10 0.10470024 465 high scalability-2008-12-14-Scaling MySQL on a 256-way T5440 server using Solaris ZFS and Java 1.7
11 0.10407566 1529 high scalability-2013-10-08-F1 and Spanner Holistically Compared
12 0.10055023 654 high scalability-2009-07-09-No to SQL? Anti-database movement gains steam – My Take
13 0.097970486 1304 high scalability-2012-08-14-MemSQL Architecture - The Fast (MVCC, InMem, LockFree, CodeGen) and Familiar (SQL)
14 0.094688646 1131 high scalability-2011-10-24-StackExchange Architecture Updates - Running Smoothly, Amazon 4x More Expensive
15 0.091866165 1181 high scalability-2012-01-25-Google Goes MoreSQL with Tenzing - SQL Over MapReduce
16 0.091156952 1018 high scalability-2011-04-07-Paper: A Co-Relational Model of Data for Large Shared Data Banks
17 0.085146621 1608 high scalability-2014-03-10-Let's Play a Game of Take It or Leave It - Game 1
18 0.084264398 196 high scalability-2007-12-30-MySQL clustering strategies and comparisions
19 0.080958918 315 high scalability-2008-05-05-HSCALE - Handling 200 Million Transactions Per Month Using Transparent Partitioning With MySQL Proxy
20 0.080730975 222 high scalability-2008-01-25-Application Database and DAL Architecture
topicId topicWeight
[(0, 0.103), (1, 0.035), (2, -0.038), (3, -0.026), (4, 0.023), (5, 0.09), (6, -0.061), (7, -0.037), (8, -0.025), (9, -0.037), (10, -0.01), (11, -0.039), (12, 0.034), (13, 0.026), (14, 0.013), (15, -0.011), (16, -0.008), (17, 0.016), (18, -0.023), (19, -0.021), (20, 0.033), (21, -0.025), (22, -0.01), (23, -0.02), (24, 0.113), (25, 0.091), (26, -0.073), (27, -0.041), (28, 0.051), (29, -0.034), (30, -0.012), (31, 0.066), (32, 0.001), (33, 0.058), (34, 0.041), (35, 0.015), (36, 0.062), (37, 0.037), (38, -0.023), (39, 0.006), (40, 0.045), (41, -0.042), (42, 0.006), (43, -0.082), (44, 0.022), (45, -0.013), (46, -0.012), (47, 0.035), (48, 0.037), (49, 0.034)]
simIndex simValue blogId blogTitle
same-blog 1 0.98901343 995 high scalability-2011-02-24-Strategy: Eliminate Unnecessary SQL
Introduction: MySQL Expert Ronald Bradford explains how one key way to improve the scalability of a MySQL server, and undoubtedly nearly every other server, is to eliminate unnecessary SQL , saying the most efficient way to improve an SQL statement is to eliminate it : The MySQL kernel can only physically process a certain number of SQL statements for a given time period (e.g. per second). Regardless of the type of machine you have, there is a physical limit. If you eliminate SQL statements that are unwarranted and unnecessary, you automatically enable more important SQL statements to run. There are numerous other downstream affects, however this is the simple math. To run more SQL, reduce the number of SQL you need to run. Ronald shows how to use mk-query-digest to look at query execution times and determine which ones can be profitably whacked. Related Articles Quora: What are the best methods for optimizing PHP/MySQL code for speed without caching?
2 0.74348706 465 high scalability-2008-12-14-Scaling MySQL on a 256-way T5440 server using Solaris ZFS and Java 1.7
Introduction: How to scale MySQL on a 32 core system with 256 threads? Diagonal scalability in a box. An impressive benchmark that achieved more than 79,000 SQL queries per second on a single 4 RU server! Is this real? If so what is the role of good old horizontal scalability? The goals of the benchmark: Reach a high throughput of SQL queries on a 256-way Sun SPARC Enterprise T5440 Do it 21st century style i.e. with MySQL and ZFS , not 20th century style i.e with OraSybInf... and VxFS Do it with minimal tuning i.e as close as possible as out-of-the-box
3 0.69123816 654 high scalability-2009-07-09-No to SQL? Anti-database movement gains steam – My Take
Introduction: In this post i wrote my view on the anti SQL database movement and where the alternative approach fits in: - SQL databases are not going away anytime soon. - The current "one size fit it all" databases thinking was and is wrong. - There is definitely a place for a more a more specialized data management solutions alongside traditional SQL databases. In addition to the options that was mentioned on the original article i pointed out the the in-memory alternative approach and how that fits into the puzzle. I used a real life scenario: scalable Social network based eCommerce site where i outlined how in-memory approach was the only option they could scale and meet their application performance and response time requirements.
4 0.67418349 410 high scalability-2008-10-13-SQL Server 2008 Database Performance and Scalability
Introduction: Microsoft SQL Server 2008 incorporates the tools and technologies that are necessary to implement relational databases, reporting systems, and data warehouses of enterprise scale, and provides optimal performance and responsiveness. With SQL Server 2008, you can take advantage of the latest hardware technologies while scaling up your servers to support server consolidation. SQL Server 2008 also enables you to scale out your largest data solutions. This white paper describes the performance and scalability capabilities of Microsoft速 SQL Server速 2008 and explains how you can use these capabilities to: * Optimize performance for any size of database with the tools and features that are available for the database engine, analysis services, reporting services, and integration services. * Scale up your servers to take full advantage of new hardware capabilities. * Scale out your database environment to optimize responsiveness and to move your data
5 0.6681965 867 high scalability-2010-07-27-YeSQL: An Overview of the Various Query Semantics in the Post Only-SQL World
Introduction: The NoSQL movement faults the SQL query language as the source of many of the scalability issues that we face today with traditional database approach. I think that the main reason so many people have come to see SQL as the source of all evil is the fact that, traditionally, the query language was burned into the database implementation. So by saying NoSQL you basically say "No" to the traditional non-scalable RDBMS implementations. This view has brought on a flood of alternative query languages, each aiming to solve a different aspect that is missing in the traditional SQL query approach, such as a document model, or that provides a simpler approach, such as Key/Value query. Most of the people I speak with seem fairly confused on this subject, and tend to use query semantics and architecture interchangeably. In Part I of this post i tried to provide quick overview of what each query term stands for in the context of the NoSQL world . Part II illustrates those ide
6 0.66799968 1025 high scalability-2011-04-16-The NewSQL Market Breakdown
8 0.63685215 252 high scalability-2008-02-18-limit on the number of databases open
9 0.63449544 1032 high scalability-2011-05-02-Stack Overflow Makes Slow Pages 100x Faster by Simple SQL Tuning
10 0.62502146 1065 high scalability-2011-06-21-Running TPC-C on MySQL-RDS
11 0.62398118 222 high scalability-2008-01-25-Application Database and DAL Architecture
12 0.61424649 961 high scalability-2010-12-21-SQL + NoSQL = Yes !
13 0.60782862 1181 high scalability-2012-01-25-Google Goes MoreSQL with Tenzing - SQL Over MapReduce
15 0.59480441 261 high scalability-2008-02-25-Make Your Site Run 10 Times Faster
16 0.59399027 770 high scalability-2010-02-03-NoSQL Means Never Having to Store Blobs Again
17 0.58092409 454 high scalability-2008-12-01-Deploying MySQL Database in Solaris Cluster Environments
18 0.58056462 16 high scalability-2007-07-16-Book: High Performance MySQL
19 0.57465935 455 high scalability-2008-12-01-MySQL Database Scale-out and Replication for High Growth Businesses
20 0.57165897 793 high scalability-2010-03-10-Saying Yes to NoSQL; Going Steady with Cassandra at Digg
topicId topicWeight
[(1, 0.116), (2, 0.105), (10, 0.022), (20, 0.278), (30, 0.077), (79, 0.176), (94, 0.099)]
simIndex simValue blogId blogTitle
1 0.87108731 370 high scalability-2008-08-18-Forum sort order
Introduction: G'day, I noticed the default sort order for the forum is to show the posts with the most replies first. That seems a bit odd for a forum. Would it not make sense to show the posts with the most recently replies first? It is possible to re-sort the forum threads that way by clicking on the "Last post" header (twice). It would seem like a more sensible default. I've checked and I see the same behaviour as both a registered (logged in) and anonymous user. Cheers - Callum .
same-blog 2 0.82870972 995 high scalability-2011-02-24-Strategy: Eliminate Unnecessary SQL
Introduction: MySQL Expert Ronald Bradford explains how one key way to improve the scalability of a MySQL server, and undoubtedly nearly every other server, is to eliminate unnecessary SQL , saying the most efficient way to improve an SQL statement is to eliminate it : The MySQL kernel can only physically process a certain number of SQL statements for a given time period (e.g. per second). Regardless of the type of machine you have, there is a physical limit. If you eliminate SQL statements that are unwarranted and unnecessary, you automatically enable more important SQL statements to run. There are numerous other downstream affects, however this is the simple math. To run more SQL, reduce the number of SQL you need to run. Ronald shows how to use mk-query-digest to look at query execution times and determine which ones can be profitably whacked. Related Articles Quora: What are the best methods for optimizing PHP/MySQL code for speed without caching?
3 0.78897732 23 high scalability-2007-07-24-Major Websites Down: Or Why You Want to Run in Two or More Data Centers.
Introduction: A lot of sites hosted in San Francisco are down because of at least 6 back-to-back power outages power outages. More details at laughingsquid . Sites like SecondLife, Craigstlist, Technorati, Yelp and all Six Apart properties, TypePad, LiveJournal and Vox are all down. The cause was an underground explosion in a transformer vault under a manhole at 560 Mission Street. Flames shot 6 feet out from the manhole cover. Over PG&E; 30,000 customers are without power. What's perplexing is the UPS backup and diesel generators didn't kick in to bring the datacenter back on line. I've never toured that datacenter, but they usually have massive backup systems. It's probably one of those multiple simultaneous failure situations that you hope never happen in real life, but too often do. Or maybe the infrastructure wasn't rolled out completely. Update: the cause was a cascade of failures in a tightly couples system that could never happen :-) Details at Failure Happens: A summary of the power
4 0.70241916 745 high scalability-2009-11-25-Brian Aker's Hilarious NoSQL Stand Up Routine
Introduction: Brian Aker gave this 10 minute lightning talk on NoSQL at the Nov 2009 OpenSQLCamp in Portland, Oregon. It's incredibly funny, probably because there's a lot of truth to what he's saying. Here are the slides and here are the notes . Found though #nosql.
5 0.66916776 1615 high scalability-2014-03-19-Strategy: Three Techniques to Survive Traffic Surges by Quickly Scaling Your Site
Introduction: Matthew Might , as a first responder to a surprise traffic surge on his inexpensive linode hosted blog, took emergency steps that you might find useful in a similar situation: Find the bottleneck. Reloading the page in firebug showed the first page took 24 seconds to load and after that everything else loaded quickly. In retrospect this burst meant the site was thread limited as the CPU was idle. Cut image sizes in half with a shell script using ImageMagick's convert. Load time is now 12 seconds. Turn dynamic content into static content using a static index.html file copied using the browser's "view source" feature. Load time is now 6 seconds. Added threads to the Apache configuration file. Load time is now 2 seconds. Crises averted. Because of this quick thinking and quick action the patient survived to serve pages another day. And in fine post-mortem tradition some of the future changes are: Run a cron job to trigger an earlier alert . Email when requ
7 0.63865066 706 high scalability-2009-09-16-The VeriScale Architecture - Elasticity and efficiency for private clouds
9 0.62622839 448 high scalability-2008-11-22-Google Architecture
10 0.62550509 680 high scalability-2009-08-13-Reconnoiter - Large-Scale Trending and Fault-Detection
11 0.62523484 380 high scalability-2008-09-05-Product: Tungsten Replicator
12 0.62144446 101 high scalability-2007-09-27-Product: Ganglia Monitoring System
13 0.61989874 1420 high scalability-2013-03-08-Stuff The Internet Says On Scalability For March 8, 2013
14 0.61872786 1494 high scalability-2013-07-19-Stuff The Internet Says On Scalability For July 19, 2013
16 0.61627614 786 high scalability-2010-03-02-Using the Ambient Cloud as an Application Runtime
17 0.61588782 1343 high scalability-2012-10-18-Save up to 30% by Selecting Better Performing Amazon Instances
18 0.61547011 1403 high scalability-2013-02-08-Stuff The Internet Says On Scalability For February 8, 2013
19 0.61446434 650 high scalability-2009-07-02-Product: Hbase