# Partition for speed

- ## Start at the beginning

  - Pick the right database for the job, if you have the choice.
  - Understand the performance issues in schema design.

- ## Application partitioning: Do What Where?

  - Work close to the data
    - Moving data to/from the client is always expensive
    - Consider latency as well as bandwidth
    - Use stored procedures where appropriate
    - Do more in SQL where appropriate - get a good book
  - Multiple simple queries with 'joins' in Perl may be faster.
  - Proprietary bulk-load is almost always faster than Perl.
  - Caching is valuable, in memory or DBM file etc, e.g. Memoize.pm
  - Mix 'n Match techniques as needed
    - experiment and do your own benchmarks
    .

Previous slide | Next slide | Back to first slide | View graphic version