Tag: performance
-
L'indicible horreur des fichiers SQLite (et les mandelbugs de corruption de profil Firefox)
En cet Halloween, je vous partage aujourd’hui une petite histoire d’horreur et quelques astuces, fruit de mes observations sur un mystérieux phénomène survenu en 2017. En fait, ce billet est resté dans mes brouillons depuis trois ans et trois semaines (essayez de battre ce record, bande de flemmards), et je me suis dit qu’il vallait…
-
Scratching some Media Library itches
Besides catching a cold and shovelling snow, this holiday season I spent some time scratching itches in Pitivi. For starters, thumbnails generation: if you’ve been using the new Pitivi, you certainly ran into this: As you can see, thumbnails were not necessarily being shown for all clips. That was not the result of a buggy…
-
GNOME 3 and login performance
How about we revive the Performance wiki page and make it a goal for GNOME 3.8 (or 3.10) to finally reach our 2005-2007 target of a “3 seconds login time”? Our current login performance is pretty bad. We do way too much I/O and processing. If you write an application or service that automatically starts…
-
Investigating Liferea's startup performance
Last week, Lars Lindner provided us with an early christmas gift when he announced that a new stable release of our beloved feed reader was now available. First, I would like to applaud him for his continued efforts over the years in maintaining this handy and high quality application. Many users like me have been…
-
Pitivi's startup time
So, since it seems everybody’s been talking about startup time these days, I’ll admit I tend to secretly obsess over that too. Well, it’s not so secret given that I’ve blogged about profiling work on Specto and PiTiVi before… anyway. I believe you should provide your developers with the fastest computers to do the development,…
-
Negotiating Performance
If you do more than basic video editing, you may have experienced those infamous “not-negotiated” errors, one of the most annoying current issues in pitivi. Users run into not-negotiated errors when there are transitions, gaps in the timeline, and effects that require compositing (such as the “alpha” filter) fail to work properly. Sometimes, if you keep…
-
GNOME 3.0's RAM usage
…is surprisingly low. Unlike what some people would make you believe, GNOME Shell & friends don’t eat 883 MB of RAM. As you can see below, baseline memory usage is under 120 MB… And you know what? That’s less than the amount of memory that GNOME 2.30 uses on startup on Ubuntu 10.04 LTS (127…
-
Improving project loading performance
When you load a project in PiTiVi, importing the clips into the “media library” (also known internally as the “source list”) is pretty fast, but inserting them in the timeline is painfully slow. So I whipped out my torture test project and spent some time profiling what’s going on using Python’s cProfile module (I talked…
-
Free my memory
My fellow Antistress argued that I should be going back from Chromium to Firefox today. I replied, “Only when it starts up in less than 3 seconds and frees my goddamn memory when closing tabs”. He then replied with the following statement: firefox a la meilleure gestion de la mémoire tous navigateurs confondus (cf tests unanimes sur…
-
Améliorer les performances de GTG
Pour les fans de la technique GTD de David Allen, Getting Things GNOME! est une révélation, un logiciel qui rend «sans douleur» l’ajout et la gestion de tâches. Je considère les fonctionnalités suivantes comme étant celles qui démarquent GTG des autres applications: La capacité d’utiliser un langage naturel, tel que “defer:20100224” ou “due:vendredi” (et on peut…