1 |
On Thursday 14 January 2010 18:25:35 Petteri Räty wrote: |
2 |
> On 01/15/2010 12:54 AM, Robin H. Johnson wrote: |
3 |
> > That top item is the largest blocker. The actual conversion time is down |
4 |
> > to 9 hours, but with more than that again in setting it up. I'd like to |
5 |
> > get the conversion time down to UNDER 4 hours. It's mostly |
6 |
> > single-threaded, and we've got lots of cores available, it just needs |
7 |
> > parallelization. We're basically dead in the water during the |
8 |
> > conversion, there is NO incremental support at all. |
9 |
> |
10 |
> Is a day really an issue? If there's something extremely urgent while |
11 |
> the conversion is going on, you can just turn CVS back on and then let's |
12 |
> try again some other day. |
13 |
|
14 |
indeed ... we've already tolerated long downtimes in different infrastructure |
15 |
pieces in our history. devs can live with advertised downtimes since the |
16 |
timing is known. it's the unknown/indefinite things that annoy people. |
17 |
-mike |