5 ms·

Finding the root cause of failure is essential, especially when you are working with large codebases. For my biggest running project, I customize about 1GB of

Finding the root cause of failure is essential, especially when you are working with large codebases. For my biggest running project, I customize about 1GB of source code not written by me. Every bug needs to be chased until one actually understands why it happened otherwise it's too risky to just make a patch that "seems" to fix it. Plus, in the process you usually learn a new and interesting thing about a previously unknown part of the codebase. Of course, very few customers actually understand the importance of this and have the budget to allow you this "luxury". Fixing the bug for most of the servers and leaving a small fraction with the old codebase to investigate the bug some more sound interesting but I couldn't be doing that.

gaius 16y ago
A gigabyte of source code!? That's the entire depot not just one tag, right?
- pmjordan 16y ago
  The Linux kernel currently is around 450MB of source code. I've worked on individual projects with 1-2MLOC, I suspect that's about 100MB of code. A couple of those don't seem all that implausible.
  - gaius 16y ago
    Hmm yulia:/usr/src# bzcat linux-source-2.6.32.tar.bz2 |wc -c 382382080 382M. Tho' is it really one "thing"? A lot of that is device drivers, loadable modules etc that no single install will ever have.
    - pmjordan 16y ago
      I guess my 450MB are from 2.6.34 and are the disk usage of the actual untarred sources that I'm working from, so my figure includes cluster off-cuts (the bytes needed to round up to the nearest 4096 for each file). It's certainly one thing in that it all uses the same build script; and any of the pieces are pretty worthless on their own.
- fierarul 16y ago
  Actually, it's just about 800MB of source code with 150MB of external dependencies. I never counted the lines of code until today but apparently just for the main language there are over 9 MLOC. Of course, this doesn't actually matter as I don't touch most of the code and the "recently active" part seems to measure only about 275 KLOC. But when a bug arrives it might take me anywhere; even so, I don't think I've visited more than 35% of the codebase.

gaius 16y ago

A gigabyte of source code!? That's the entire depot not just one tag, right?

pmjordan 16y ago
The Linux kernel currently is around 450MB of source code. I've worked on individual projects with 1-2MLOC, I suspect that's about 100MB of code. A couple of those don't seem all that implausible.
- gaius 16y ago
  Hmm yulia:/usr/src# bzcat linux-source-2.6.32.tar.bz2 |wc -c 382382080 382M. Tho' is it really one "thing"? A lot of that is device drivers, loadable modules etc that no single install will ever have.
  - pmjordan 16y ago
    I guess my 450MB are from 2.6.34 and are the disk usage of the actual untarred sources that I'm working from, so my figure includes cluster off-cuts (the bytes needed to round up to the nearest 4096 for each file). It's certainly one thing in that it all uses the same build script; and any of the pieces are pretty worthless on their own.
fierarul 16y ago
Actually, it's just about 800MB of source code with 150MB of external dependencies. I never counted the lines of code until today but apparently just for the main language there are over 9 MLOC. Of course, this doesn't actually matter as I don't touch most of the code and the "recently active" part seems to measure only about 275 KLOC. But when a bug arrives it might take me anywhere; even so, I don't think I've visited more than 35% of the codebase.