别以为你穿上马甲,我就不认得你了
•Download as KEY, PDF•
1 like•323 views
This document discusses NoSQL databases and key value stores that are schema-less. It mentions that key value databases are useful for caching and common ones include memcached. It also lists some web 2.0 technologies like RSS, Twitter, Facebook, and companies that use key value stores like Ning and Litt.
Report
Share
Report
Share
Recommended
Web technology
LESS is a CSS pre-processor that extends CSS with features like variables, mixins, functions and nested rules to make CSS more powerful, maintainable and dynamic. It allows variables, operations and functions to be used in CSS and compiles LESS files into regular CSS files. LESS makes writing stylesheets easier with a modular approach and enables dynamic properties in CSS.
Drupalcamp Estonia - High Performance Sites
Rami Jarvinen discusses optimizing performance on Drupal sites. He outlines several caching layers that can be implemented including PHP opcode caching, Drupal internal caching, page caching, and reverse proxy caching using Boost or Varnish. He also discusses scaling Drupal through techniques such as MySQL master-slave configuration, serving static files from Nginx/lighttpd, and adding frontend servers. Profiling with tools like Xdebug can help identify SQL bottlenecks to optimize. The optimal caching and performance strategy depends on each site's specific usage and hosting environment.
WordCamp RVA
The document discusses optimizing WordPress performance. It recommends minimizing frontend assets like images, implementing caching for assets and application chunks, optimizing themes and plugins, and choosing efficient server setups. Specific plugins like W3 Total Cache and a CDN can improve performance by up to 10 times by caching static content. Nginx is presented as a faster alternative to Apache. Overall, the key takeaways are to simplify code, minimize requests, optimize caching, and reduce payload sizes to improve perceived and actual performance.
Drupal caching
- Drupal relies heavily on SQL queries which can burden databases. Caching improves performance by reducing database queries.
- There are different levels of caching in Drupal - from internal block/page caching, to HTTP caching using a reverse proxy, CDN, or custom caching with Drupal's cache API.
- For high traffic sites, saving the Drupal cache to memory (e.g. using memcached) rather than the database is recommended. Opcode caching like APC also provides significant performance gains.
- Profiling a site is important to identify bottlenecks and determine the appropriate caching strategy based on factors like site content and hosting environment.
Performance Web
The document discusses factors that affect website performance, including front-end elements like CSS, JavaScript, images, and back-end elements like caching, threading, and database queries. It notes that only 10-20% of response time is spent on downloading HTML, so focus should be on optimizing other parts of the page load. It also outlines the anatomy of an HTTP request and lists 14 rules for improving performance, such as reducing HTTP requests, using content delivery networks, gzipping components, and making AJAX cacheable. It emphasizes that teams should regularly audit performance and prioritize optimizations.
Cache all the things - A guide to caching Drupal
This document discusses caching strategies for Drupal websites. It recommends caching everything possible, from code-level caching using Drupal's cache API, to resource caching of assets like CSS and JavaScript using modules like Boost or Varnish, to data caching of the database using Memcached. It also covers third-party caching options provided by content delivery networks like Akamai and Cloudflare. The key is to implement caching at multiple layers from the code to resources to external networks to optimize site performance and protect against issues. Debugging requires analyzing caching headers and being able to selectively flush caches at different layers.
Иван Глушков (Echo)
This document provides an overview of NewSQL databases. It discusses the history of SQL and relational databases and how requirements have changed with huge, growing datasets generated by devices. It describes how NoSQL databases addressed scalability but sacrificed SQL and ACID support. NewSQL databases aim to provide the scalability of NoSQL with the SQL interface and transactional support of traditional databases. The document outlines various NewSQL approaches and database examples like NuoDB, VoltDB, ScaleDB, and ClustrixDB and how they achieve horizontal scaling and high performance. In conclusions, it states that NewSQL is an established trend but it's hard to pick one as the best option since they are not on a common scale.
Drupal Performance
This document discusses various techniques for improving Drupal performance and scaling. It covers optimizing hardware resources like RAM and PHP opcode caches. Front-end optimizations include JavaScript and CSS aggregation, caching, and compression. Database engines and using a content delivery network can help. The Pressflow distribution of Drupal is optimized for performance. Monitoring and measuring performance is also important.
Recommended
Web technology
LESS is a CSS pre-processor that extends CSS with features like variables, mixins, functions and nested rules to make CSS more powerful, maintainable and dynamic. It allows variables, operations and functions to be used in CSS and compiles LESS files into regular CSS files. LESS makes writing stylesheets easier with a modular approach and enables dynamic properties in CSS.
Drupalcamp Estonia - High Performance Sites
Rami Jarvinen discusses optimizing performance on Drupal sites. He outlines several caching layers that can be implemented including PHP opcode caching, Drupal internal caching, page caching, and reverse proxy caching using Boost or Varnish. He also discusses scaling Drupal through techniques such as MySQL master-slave configuration, serving static files from Nginx/lighttpd, and adding frontend servers. Profiling with tools like Xdebug can help identify SQL bottlenecks to optimize. The optimal caching and performance strategy depends on each site's specific usage and hosting environment.
WordCamp RVA
The document discusses optimizing WordPress performance. It recommends minimizing frontend assets like images, implementing caching for assets and application chunks, optimizing themes and plugins, and choosing efficient server setups. Specific plugins like W3 Total Cache and a CDN can improve performance by up to 10 times by caching static content. Nginx is presented as a faster alternative to Apache. Overall, the key takeaways are to simplify code, minimize requests, optimize caching, and reduce payload sizes to improve perceived and actual performance.
Drupal caching
- Drupal relies heavily on SQL queries which can burden databases. Caching improves performance by reducing database queries.
- There are different levels of caching in Drupal - from internal block/page caching, to HTTP caching using a reverse proxy, CDN, or custom caching with Drupal's cache API.
- For high traffic sites, saving the Drupal cache to memory (e.g. using memcached) rather than the database is recommended. Opcode caching like APC also provides significant performance gains.
- Profiling a site is important to identify bottlenecks and determine the appropriate caching strategy based on factors like site content and hosting environment.
Performance Web
The document discusses factors that affect website performance, including front-end elements like CSS, JavaScript, images, and back-end elements like caching, threading, and database queries. It notes that only 10-20% of response time is spent on downloading HTML, so focus should be on optimizing other parts of the page load. It also outlines the anatomy of an HTTP request and lists 14 rules for improving performance, such as reducing HTTP requests, using content delivery networks, gzipping components, and making AJAX cacheable. It emphasizes that teams should regularly audit performance and prioritize optimizations.
Cache all the things - A guide to caching Drupal
This document discusses caching strategies for Drupal websites. It recommends caching everything possible, from code-level caching using Drupal's cache API, to resource caching of assets like CSS and JavaScript using modules like Boost or Varnish, to data caching of the database using Memcached. It also covers third-party caching options provided by content delivery networks like Akamai and Cloudflare. The key is to implement caching at multiple layers from the code to resources to external networks to optimize site performance and protect against issues. Debugging requires analyzing caching headers and being able to selectively flush caches at different layers.
Иван Глушков (Echo)
This document provides an overview of NewSQL databases. It discusses the history of SQL and relational databases and how requirements have changed with huge, growing datasets generated by devices. It describes how NoSQL databases addressed scalability but sacrificed SQL and ACID support. NewSQL databases aim to provide the scalability of NoSQL with the SQL interface and transactional support of traditional databases. The document outlines various NewSQL approaches and database examples like NuoDB, VoltDB, ScaleDB, and ClustrixDB and how they achieve horizontal scaling and high performance. In conclusions, it states that NewSQL is an established trend but it's hard to pick one as the best option since they are not on a common scale.
Drupal Performance
This document discusses various techniques for improving Drupal performance and scaling. It covers optimizing hardware resources like RAM and PHP opcode caches. Front-end optimizations include JavaScript and CSS aggregation, caching, and compression. Database engines and using a content delivery network can help. The Pressflow distribution of Drupal is optimized for performance. Monitoring and measuring performance is also important.
Lean startup模式简介
The document introduces the Lean Startup model which focuses on building a minimum viable product, testing business model hypotheses using the Business Model Canvas tool, and engaging in customer development. It discusses key concepts like TAM/SAM/TM from the Stanford Venture Lab and pivoting. The Lean Startup mode aims to shorten product development cycles through an iterative process of testing assumptions with customers and making databased decisions.
别以为你穿上马甲，我就不认得你了
This document discusses NoSQL databases and key value stores that are schema-less. It mentions that key value databases are useful for caching and common ones include memcached. It also lists some web 2.0 technologies like RSS, Twitter, Facebook, and companies that use key value stores like Ning and Litt.
More Related Content
More from caleng
Lean startup模式简介
The document introduces the Lean Startup model which focuses on building a minimum viable product, testing business model hypotheses using the Business Model Canvas tool, and engaging in customer development. It discusses key concepts like TAM/SAM/TM from the Stanford Venture Lab and pivoting. The Lean Startup mode aims to shorten product development cycles through an iterative process of testing assumptions with customers and making databased decisions.
别以为你穿上马甲，我就不认得你了
This document discusses NoSQL databases and key value stores that are schema-less. It mentions that key value databases are useful for caching and common ones include memcached. It also lists some web 2.0 technologies like RSS, Twitter, Facebook, and companies that use key value stores like Ning and Litt.
More from caleng (6)
别以为你穿上马甲,我就不认得你了
- 2. NOSQL
- 4. schema less
- 6. key value DB
- 16. web 2.0
- 17. rss
- 19. twitter facebook
Editor's Notes
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n