| 1 |
On Sunday 12 June 2005 00:34, Brian wrote: |
| 2 |
> I believe I have found an error in the way porthole is using portage. |
| 3 |
> |
| 4 |
> After an emerge sync which had a large number of update downloaded. I |
| 5 |
> switched to our upgrades view which stated building the treeview. |
| 6 |
> |
| 7 |
> It was extremely slow, something I had noticed from time to time but did |
| 8 |
> not know why. It usually finished before I determined why. This time |
| 9 |
> using gnome system monitor I was able to determine that it was portage |
| 10 |
> doing repeated calls to "ebuild.sh depend" for different packages. |
| 11 |
> |
| 12 |
> After it is complete a db reload and new upgrades list is quick again. |
| 13 |
> |
| 14 |
> Am I correct in that the imported instance of portage was still using |
| 15 |
> the old metadata cache at the time of import? Even though the cache was |
| 16 |
> updated at the end of the sync. After a sync we should re-initialize |
| 17 |
> our instance of portage for it to use the new cache? |
| 18 |
|
| 19 |
Correct. I'm not sure what will happen in the future, but adding checks for |
| 20 |
this into the current design will noticably slow down the general case (where |
| 21 |
the cache isn't changed by external processes). |
| 22 |
|
| 23 |
Regards, |
| 24 |
Jason Stubbs |
Archives