Forum Posts

As I mentioned earlier in this forum, Ohloh causes severe DOS to my network every week when it processes the GraphicsMagick enlistments. The GraphicsMagick CVS repository is surely one of the older ... [More] and larger ones on the net. Outbound bandwith from my site is limited (somewhere around 80 kilobytes/second). When Ohloh does its weekly processing, it seems to use the least efficient algorithm possible and without enabling data compression. When only a tiny change has been committed since the previous enlistment run (taking only a second or two for CVS update from a remote location), Ohloh will still arrange to peg the link to maximum latency for a full day. It is as if it starts from scratch each week, pulling each and every file revision since the repository was created 12 years ago. That would be gigabytes of data to transfer. This network is used to support the needs of other projects such as libpng and needs to be reasonably available. This abuse is not acceptable to me. If Ohloh does not fix its broken algorithm, I will be forced to remove the enlistments. Today I had to kill off the CVS server process just so I could post to this forum. Bob [Less]

The GraphicsMagick enlistments failed a couple of months ago. Something apparently gotten jammed. Nothing has changed on the server end. Also, as mentioned before, ohloh severely jams up the server ... [More] due to doing many simultaneous requests. There are are multiple enlistments in order to pick up all of the submodules since ohloh does not seem to support a CVS modules file. Probably all of those enlistments are getting pulled in parallel. Bob [Less]

When Ohloh was indexing correctly, it caused no problem for my site. When it went haywire, it maxed it out the transfer rate. Any site which has less outbound bandwith than Ohloh has inbound ... [More] bandwidth would have been brought to its knees. It seems wise for Ohloh to estimate the available bandwidth from the site it is sucking from and throttle back if the remote site is slower. [Less]

CVS itself does not version directories. If most projects do not use a modules file then it is likely because they have not read the documentation or they are lazy. Regardless, I re-registered the ... [More] problem module using a physical directory path rather than a module name and it took just a few minutes rather than a day. [Less]

Module entries are defined via the CVSROOT/modules file and what is why they are called 'modules'. Use of physical directories is only a fallback and not actually recommended.

This is absolutely nuts. At the current rate it will take days to update for this tiny bit of the source code repository. I am not sure what it is trying to do but it is now at "Step 1 of 3: ... [More] Downloading source code history (Running 195/535)" and is keeping the ping times pegged to 16 seconds. It has been like this for 14 hours already, entirely blocking any other access to my site. I will attempt to shut the access down now. [Less]

My site is getting pounded again due to this module. I wonder what is so strange about it that it requires so many accesses and bandwidth to evaluate?

I decided to add back the enlistment which was causing the problem (VisualMagick). We shall see if the problem resumes. There is apparently something strange about this module which caused ohloh to ... [More] churn on it for maybe 10 hours straight. The other modules updated quickly. [Less]

A strange thing is that most of the project was absorbed fairly quickly but just one fairly small module seemed to take all day as if there was something special about it. So I de-registered the ... [More] module and killed off the CVS processes. I know that I need to buy a better router which can better load-share the outbound traffic. [Less]

It seems that ohloh is quite aggressive when accessing the CVS server. This may be ok for high bandwidth sites but my site has a usable 60 kilo bytes outbound transfer bandwidth ("business class" ... [More] ADSL). For 24 hours now my site has experienced extremely high latencies and has been essentially unusable due to aggressive access by the ohloh bots as they access the rather large GraphicsMagick CVS repository. At times there has been access from three machines at once. The pounding continues so I can barely access this web site. Is this normal? Is there a way to tune-down the transfer rates so that ohloh is non-invasive like most 'bots'? Thanks, Bob [Less]