Yes, it seems likely that we're connecting a bit more often than once an hour, as we are currently trying to import 12 projects once every 6 hours, not to mention that cscvs doesn't use persistent connections:
(a review_status of 20 means active in this context).
I was aware that the apache admins had a propensity to get upset over this, and _I_ have avoided approving imports from there. I guess I didn't pass this information on as well as I could have done to others who review imports.
"update codeimport set review_status = 30 where svn_branch_url like '%apache%'" will stop all import attempts.
If you can convince the admins that connection count is not a very good measure of the load we're placing on the server, that would be good (cscvs makes lots of connections, but they're all very small/cheap), I had a hard time trying to get the admin I spoke to to even consider this.
If we want to import from svn.apache.org (and we probably do) maybe we can keep a svnsync-ed copy of the repo somewhere? I imagine it takes up rather a lot of disk though...
Yes, it seems likely that we're connecting a bit more often than once an hour, as we are currently trying to import 12 projects once every 6 hours, not to mention that cscvs doesn't use persistent connections:
https:/ /pastebin. canonical. com/13707/
(a review_status of 20 means active in this context).
I was aware that the apache admins had a propensity to get upset over this, and _I_ have avoided approving imports from there. I guess I didn't pass this information on as well as I could have done to others who review imports.
"update codeimport set review_status = 30 where svn_branch_url like '%apache%'" will stop all import attempts.
If you can convince the admins that connection count is not a very good measure of the load we're placing on the server, that would be good (cscvs makes lots of connections, but they're all very small/cheap), I had a hard time trying to get the admin I spoke to to even consider this.
If we want to import from svn.apache.org (and we probably do) maybe we can keep a svnsync-ed copy of the repo somewhere? I imagine it takes up rather a lot of disk though...