• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
TYPO3 Scalability for high traffic sites
 

TYPO3 Scalability for high traffic sites

on

  • 5,818 views

 

Statistics

Views

Total Views
5,818
Views on SlideShare
5,791
Embed Views
27

Actions

Likes
2
Downloads
0
Comments
0

1 Embed 27

http://www.slideshare.net 27

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Probability of failure increases with more components
  • Realistic goals: Traffic per time period, concurrent users, response time

TYPO3 Scalability for high traffic sites TYPO3 Scalability for high traffic sites Presentation Transcript

  • TYPO3 Scalability for high traffic Websites
    Presenter: Dan Osipov
    http://danosipov.com
    Twitter: @danosipov
  • About me
    Work with TYPO3 full time since 2007
    Used TYPO3 for high traffic dynamic news sites
    DAM Team leader
    Author of TYPO3 4.3 Multimedia Cookbook from Packt
  • What is Scalability?
    “Desirable property of a system which indicates its ability to either handle growing amounts of work in a graceful manner or to be readily enlarged.”[1]
    [1] http://en.wikipedia.org/wiki/Scalability
  • Why scale?
    Support more traffic
    Offer better response time
    High availability & minimum downtime
  • Vertical scaling
  • Vertical scaling
  • Vertical scaling
  • Horizontal scaling
  • How to build a scalable system?
    Develop benchmarks
    Optimize the site
    Find bottlenecks
    Experiment
    Art more than a science
  • Benchmarking
    Benchmarks: measurable goals you can use to track progress
    ab
    Jmeter
    Profiling
    Monitoring
  • Caching
    Cache everything that can be cached
    TYPO3 Cache
    Use different backends (TYPO3 >4.3)
    MySQL Query Cache
    PHP Bytecode cache
    eaccelerator
    APC
    X-Cache
  • Separating Processing & DB
  • Separating Processing & DB
    Point TYPO3 to a different host for DB
    Optimize servers for their function
    Multiple processors for processing server
    Fast disks and RAM for DB server
    Compress data between processing & DB server
    $TYPO3_CONF_VARS['SYS']['dbClientCompress']
  • Scaling application servers
  • Scaling application servers
    Load balancer
    Round robin DNS
    Hardware load balancer
    Software load balancer (nginx)
    Centralize storage
    Fileadmin on NFS
    rsync
  • Scaling application servers
  • Scaling DB servers
  • Scaling DB servers
    Sharding
    Master-Slave Replication
    Easy to set up for most DB systems
    t3p_scalable
    Read (SELECT) requests go to slave servers
    Write (INSERT, UPDATE, DELETE, etc) requests go to the master
  • Scaling DB servers
  • Scaling File System
  • Scaling File System
    Amazon S3
    cdnfiles
    Replaces “fileadmin/”, “uploads/”, “typo3temp/pics/” links to CDN equivalents
    Isn’t responsible for uploading or maintaining CDN versions
  • High Availability
  • High Availability
  • High Availability
  • Limitations
    Single Master DB
    Every FE request requires a connection to the master
    100% availability (failover in catastrophic cases)
    Difficult to scale
  • Cloud computing
    Scalability on demand
    Easy to launch required servers & shut them down when traffic falls
    EC2
    Joyent
    Rackspace
  • Questions?
    Thank you for listening!