Bug 84882 - Reminder: committing large projects cause problems
Summary: Reminder: committing large projects cause problems
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: 3.1 M6   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-10 07:54 EST by Oyvind Harboe CLA
Modified: 2005-03-17 16:28 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Oyvind Harboe CLA 2005-02-10 07:54:47 EST 
I've got two different projects I'm working on where I'm committing >50000 files
to CVS.

Once the files are committed, things work pretty well, but the commit process
itself is painful from within Eclipse.

E.g. the Commit dialog lists all the files that are to be committed recursively
and it seems like the Eclipse GUI is unresponsive due to it trying to create a
TreeView w/50000 files.

Øyvind
Comment 1 Oyvind Harboe CLA 2005-02-11 12:39:22 EST 
I've verified that the CVS command line tools handles these projects without any
visible strain or strange error messages.

Øyvind
Comment 2 Michael Valenta CLA 2005-02-11 12:46:26 EST 
I suspect the problem is the scalability of the tree view (and the mechanism 
used to populate it). The options to handle this are to introduce a preference 
for diabling the commit preview or to have a threshold that, when exceeded, 
will not preview the outgoin changes. I like the threshold idea myself. It 
would work out of the box and setting the threshold to 0 would, in essence, 
disable the preview for those who never want it.
Comment 3 Oyvind Harboe CLA 2005-02-11 14:29:14 EST 
>I suspect the problem is the scalability of the tree view (and the mechanism 
>used to populate it). The options to handle this are to introduce a preference 
>for diabling the commit preview or to have a threshold that, when exceeded, 
>will not preview the outgoin changes. I like the threshold idea myself. It 
>would work out of the box and setting the threshold to 0 would, in essence, 
>disable the preview for those who never want it.

No more options! :-) 

How about hardcoding the maximum to, say 1000, and leave an open "Fix in the
future" PR for the scalability problem?

This really is an open problem until solved properly anyway.


Øyvind
Comment 4 Michael Valenta CLA 2005-03-17 16:28:42 EST 
I've added the display threshold. Fix released to HEAD.