nautilus integration too slow in large trees
Bug #477805 reported by
mati
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar GTK+ Frontends |
Triaged
|
Medium
|
Unassigned |
Bug Description
I don't know if it's actually Nautilus' fault or bzr-gtk's, but navigating through a large project is painfully slow. Either way, in order for Bazaar to take over the world, the culprit should be fixed.
Also: why does it require to manually copy files to user's home directory? It should be done automatically.
Changed in bzr-gtk: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: nautilus-bzr |
To post a comment you must log in.
I find it unusably slow too, taking minutes to navigate between directories when browsing.
But in my case, this may not be directly attributable to Olive....
I have a Virtualbox VM with Ubuntu Hardy Heron running on it. This acts as a development server, mimicing a live environment. The files on this Virtualbox are under Bazaar control. The project consists of about
To make changes to the code I mount the development directory using sshfs, and alter the code. Obviously sshfs is an overhead that is redundant since the Virtualbox is on the local machine. This may be what is slowing Olive down so much. Or it could be that Olive is hugely inefficient over networks, even if it is a virtual network.
I'm running a Q6600 quad core Intel with 8GB memory. Other operations with the virtual machine are speedy. The virtual machine has 2GB of the 8 dedicated to it.
I have just under 15,000 files under Bazaar, stored in about 900 directories.