Virus Scanners?
2004-07-17 00:25![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
blufiveDon't talk to me about Virus Scanners.
Especially the newly-updated sort that, when I run a build on my workstation, decide to go on a computationally-intensive bug-hunt involving *every* *single* *file* accessed (note, accessed) by the build.
This is a Java build. So that would be several hundred CVS administration files, ~3500 source code files, a couple of dozen code libraries, ~3500 generated class files, ~3500 generated class files (again) as they get zipped up into a library, the built library as it gets copied to its target location and the built library (yet again), together with a few hundred JSP, HTML, XML, JPG and GIF files, as they all get zipped up into a deployment package.
A process that used to take about 1-2 minutes, with maybe a few seconds of real CPU-hogging as the main compilation happened, now takes 5 minutes, mostly with the CPU pegged at 100% by an over-enthusiastic process that thinks I don't need no steenkin' UI. And the only reason it doesn't spend even more time at 100% is that the hard drive can't keep up with all the I/O requests. Joy.
Oh, then I get to start my local web server, and watch it scan the deployment package (again), the libraries (again. You know, they haven't changed in the last 30 minutes) and all the temporary files that the server creates as it compiles the JSPs. Used to take 20-30 seconds (thanks to some code I *really* want to optimise, but can't as we have bigger fish to fry) now takes about 2-5 minutes, depending how sadistic the VS is feeling.
IS assure me that this is not normal, and they'll look into it. They better had do, or I'll have a total sense-of-humour bypass within a week.
Oh, and the bloody corporate spam-trap is eating every document with more than the microsoft-mandated number of dots in the file name. That'll be every document produced by our entire division for the last two years needing renaming before we can email them to anyone, then.
This has been a general-purpose rant brought to you by a pissed-off programmer. Thankyou, and goodnight.
Especially the newly-updated sort that, when I run a build on my workstation, decide to go on a computationally-intensive bug-hunt involving *every* *single* *file* accessed (note, accessed) by the build.
This is a Java build. So that would be several hundred CVS administration files, ~3500 source code files, a couple of dozen code libraries, ~3500 generated class files, ~3500 generated class files (again) as they get zipped up into a library, the built library as it gets copied to its target location and the built library (yet again), together with a few hundred JSP, HTML, XML, JPG and GIF files, as they all get zipped up into a deployment package.
A process that used to take about 1-2 minutes, with maybe a few seconds of real CPU-hogging as the main compilation happened, now takes 5 minutes, mostly with the CPU pegged at 100% by an over-enthusiastic process that thinks I don't need no steenkin' UI. And the only reason it doesn't spend even more time at 100% is that the hard drive can't keep up with all the I/O requests. Joy.
Oh, then I get to start my local web server, and watch it scan the deployment package (again), the libraries (again. You know, they haven't changed in the last 30 minutes) and all the temporary files that the server creates as it compiles the JSPs. Used to take 20-30 seconds (thanks to some code I *really* want to optimise, but can't as we have bigger fish to fry) now takes about 2-5 minutes, depending how sadistic the VS is feeling.
IS assure me that this is not normal, and they'll look into it. They better had do, or I'll have a total sense-of-humour bypass within a week.
Oh, and the bloody corporate spam-trap is eating every document with more than the microsoft-mandated number of dots in the file name. That'll be every document produced by our entire division for the last two years needing renaming before we can email them to anyone, then.
This has been a general-purpose rant brought to you by a pissed-off programmer. Thankyou, and goodnight.
