Monday, January 25th, 2010 Posted in mysql, performance, pt_PT | No Comments »
Em Setembro escrevi sobre as consequências de deixar ao acaso o tamanho e character set de campos VARCHAR. Entretanto gostaria de complementar as observações com o que escrevo abaixo. A mistura ... Read more..Thursday, September 24th, 2009 Posted in mysql, performance, pt_PT | 3 Comments »
Apesar do tamanho dos campos VARCHAR não influenciar o tamanho dos índices, este tipo de dados (e outros semelhantes) comportam uma série de características que podem afectar seriamente a performance. ... Read more..Saturday, August 22nd, 2009 Posted in en_US, mysql, performance | No Comments »
Although my previous conclusions about VARCHAR influence on index size could be quite storage engine specific, I'd like to see if we can extend them to InnoDB, so I took ... Read more..Thursday, August 20th, 2009 Posted in en_US, mysql, performance | 4 Comments »
I was trying to determine if the storage size of a VARCHAR field in MySQL had any fixed influence in the key size. I've created a few tables, but an ... Read more..Monday, July 6th, 2009 Posted in en_US, linux driver, mysql, performance, sugarcrm | No Comments »
Following my tests with DATETIME vs vs TIMESTAMP vs INT performance and benchmarking with MyISAM storage engine, I've wondered about the performance impact using InnoDB, which is usually more peaky ... Read more..Monday, July 6th, 2009 Posted in en_US, mysql, performance | 4 Comments »
Recently there was a discussion about DATETIME vs TIMESTAMP vs INT performance and storage requirements. If one setup was bound to disk usage, one would expect INT to perform better, ... Read more..