Update
This commit is contained in:
@@ -53,22 +53,6 @@ out exact error is try to parse error string (which is localized).
|
||||
==> database
|
||||
* We should have a DB performance test suite to find important points to make faster,
|
||||
if we cannot measure, we cannot improve.
|
||||
|
||||
* History, and Summary-Description objects should be kept in seperate db files. This way
|
||||
we can have faster searches and probably faster access to packages and better memory footprint
|
||||
|
||||
* For big objects with many member objects (Package, from pisi.metadata) we might investigate
|
||||
writing our own simple serialization routines for some objects like Conflicts or additionalfiles.
|
||||
|
||||
* context singleton is a mess. Maybe we should consider another approach to access common db objects
|
||||
|
||||
* ComponentDB should not hold lists of Packages that belongs to it. A new index for components to package DB
|
||||
should be enough.
|
||||
|
||||
* Current implementation of repository system is suboptimal. We add every package to a Dictionary as value
|
||||
and repository name as key and add that dictionary to db. For example if I am adding package foo to
|
||||
packages db, I am actually adding, a Dictionary with ["repotype", foo] to db.
|
||||
This is cheap, bloated and slow. We must have different repository databases for packages.
|
||||
|
||||
==> class attributes
|
||||
* In some classes there are some attributes assigned but never
|
||||
@@ -104,11 +88,6 @@ http://liste.uludag.org.tr/uludag-commits/2007-February/010070.html
|
||||
* Improve logging with all needed update/downgrade/install/remove information so one can easily find the history of packages,
|
||||
currently PiSi wrotes everyting into logs which is not usefull. Also this information can be used for rollback and reporting.
|
||||
|
||||
==> operations.py and atomicoperations.py
|
||||
|
||||
* These modules have gone so big and become untraceable... divide all operations to their related modules
|
||||
under a pisi.operations module...
|
||||
|
||||
==> function code lengths
|
||||
|
||||
* we have some functions that goes pages long... divide all of them to small digestable chunks..
|
||||
|
||||
Reference in New Issue
Block a user