Project

General

Profile

[logo] 
 
Home
News
Activity
About/Contact
Major Tools
  Dinotrace
  Verilator
  Verilog-mode
  Verilog-Perl
Other Tools
  IPC::Locker
  Parallel::Forker
  Voneline
General Info
  Papers

Issue #665

speedup s4 update after viewspec change

Added by Brad Dobbie over 6 years ago. Updated over 2 years ago.

Status:
Feature
Priority:
Normal
Assignee:
% Done:

0%

Estimated time:
1.00 h

Description

A viewspec with a bunch of switched fields is kind of annoying because SVN can only switch one item per client call. Thus checking out such an area will be slow, but there is no way to get around that. When making an incremental viewspec change, the update should be pretty fast. Unfortunately it isn't. S4 goes through each view item and determines weather a switch or an update is necessary. Switches need to be separated out into their own SVN client calls, but the updates should be able to be batched up into a single SVN client call. This should provide significant speedup when making incremental viewspec changes.

Existing:
s4: Updating xyz_1.1/rtl/foo/foo.csr
At revision 158355.
s4: Updating xyz_1.1/rtl/bar/bar.csr
At revision 158355.
s4: Updating xyz_1.1/rtl/baz/baz.csr
At revision 158355.
Proposed:
s4: Updating xyz_1.1/rtl/foo/foo.csr xyz_1.1/rtl/bar/bar.csr xyz_1.1/rtl/baz/baz.csr
At revision 158355.

I took a look a ViewSpec.pm, and it should be fairly easy modify the apply_viewspec() subroutine to push the Update items into a list and process them at the end of the foreach my $action (@{$self->{vs_actions}}) loop.

History

#1 Updated by Wilson Snyder over 2 years ago

  • Status changed from New to Feature
  • Priority changed from High to Normal

Also available in: Atom