incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Van Steenburgh" <vansteenbu...@users.sf.net>
Subject [allura:tickets] #6801 Options to parallelize last_commit_ids
Date Tue, 19 Nov 2013 23:26:55 GMT
- **QA**: Tim Van Steenburgh



---

** [tickets:#6801] Options to parallelize last_commit_ids**

**Status:** code-review
**Labels:** performance 
**Created:** Sat Oct 26, 2013 04:22 AM UTC by Dave Brondsema
**Last Updated:** Fri Nov 15, 2013 06:27 PM UTC
**Owner:** Cory Johns

For faster `last_commit_ids` processing, we should run N `git log` commands in parallel. 
We may want to require minimum number of files/dirs before running in parallel if there is
significant enough overhead in spinning up new threads.  (See runtests.py for an example of
a threadpool running external commands)

This will largely remove the benefit of the current iterative approach, which can short-circuit
some commands if files/dirs have the same last commit.  We can try to keep some of it, though,
for cases where the parallelism is less than the total number of files/dirs.


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message