¿Su Base de Datos PostgreSQL está lenta? ¿Observa alta latencia, muchas queries lentas o incluso los clientes se quejan? Si necesita un ajuste de performance porque simplemente quiere tener una base de Datos rápida y confiable, usted está en el lugar indicado.

Ajuste de almacenamiento en PostgreSQL

El ajuste de performance implica también un ajuste de almacenamiento. Una buena performance de almacenamiento de datos es clave para que el funcionamiento general de PostgreSQL sea óptimo, pero no es lo único: incluso cosas como el filesystem o RAID level correcto puede hacer la diferencia.

Lo ayudaremos a mejorar su sistema I/O para que esté acorde a sus necesidades.

¿Tenemos que comprar más discos?

Nuestro equipo de consultores PostgreSQL pueden responder a esa pregunta – no hay necesidad de comprar más hardware a menos que sea expresamente necesario. PostgreSQL tiene todos los medios para determina dónde están los cuellos de botella. Nuestro ojo entrenado puede distinguir fácilmente cuándo el problema de performance se debe a I/O y hacer las recomendaciones pertinentes que realmente hagan una diferencia

PostgreSQL performance tuning chart

Ajustes de parámetros de memoria en PostgreSQL

¿No sabe qué valores ingresar en los parámetros de postgresql.conf? No se preocupe, nosotros podemos ajustar postgresql.conf por usted. Si está buscando ajustes de memoria, los siguientes valores serán relevantes:

PostgreSQL Performance Tuning

 

  • shared_buffers: The PostgreSQL I/O cache
  • work_mem: Parameter to tune sorting, grouping, etc.
  • maintenance_work_mem: Speed up administrative tasks such as VACUUM, etc.
  • temp_buffers: Speed up temporary tables
  • effective_cache_size: Tell PostgreSQL about the amount of memory in your server.
  • wal_buffers: More speed for the transaction log

Tuning memory settings really makes sense. Customers have reported staggering performance improvements, which can really improve user experience.

PostgreSQL Performance Tuning table partitioning

Optimizing table partitioning

If tables grow beyond a certain size, it can make sense to partition your tables. Since the introduction of version 10.0, PostgreSQL offers native table partitioning. Built in-partitioning has the advantage that you don’t have to use external tools anymore and that there is no need to do things manually.

In PostgreSQL 10.0 we will have:

  • range-partitioned
  • list-partitioned

In the future more features such as hash partitioning might be available.

The new syntax in PostgreSQL 10.0:

The idea behind partitioning is to split data into smaller chunks. The questions naturally arising are:

  • When should developers start to partition a table?
  • How should a table be partitioned?
  • What are the benefits?
  • What is the downside?

Don’t worry. Our team of experts is here to answer exactly those questions.

Contact us

Finding and fixing slow queries

The database is slow, please make it faster.

I think each of us has heard something like that in the past already. PostgreSQL offers all the means necessary to spot slow queries and to figure out exactly what is going on.

If you are not sure what is really slow on your system, don’t worry – we are here to help you. We provide a tool called pgwatch2, which is there to help you and to spot problems. In addition to that, we can help to properly understand the data collected by PostgreSQL so that you can your developers and work on the real problems, which are slowing things down.

Breaking database performance barriers

Deploying missing indexes

Did you know that missing indexes cause at least half of all performance problems? A single missing index on a large table can seriously harm performance and reduce throughput in a counterproductive fashion.

Always check for missing indexes.

Whenever performance is bad and whenever queries feel somewhat small, contact our support team and we will check your system to figure out if indexing has been done properly.

Rewriting slow queries

If indexing, improving storage, changing memory parameters, and so on are still not enough – maybe rewriting a query can be helpful?
In some cases, small changes to a query can make a large difference (here is an example of such a change: http://www.cybertec-postgresql.com/func-hidden-performance-issues). Rewriting queries needs a lot of expertise, which we can gladly provide to customers around the globe.

Professional help

Contact us today to receive your personal offer from Cybertec. We offer timely delivery, professional handling, and over 17 years of PostgreSQL experience.

Contact us