On Fri, 18 Jun 2004, Joshua D. Drake wrote:
> Hello,
>
> I am also considering moving plPerlNG to SourceForge. Although I believe
> that pgFoundry is a good idea, there just isn't enough bandwidth and
> hardware support behind the project to make it usable.
bandwidth related, I'm suspecting that alot of the problem is the Linksys
switch we threw in when we first setup the servers ... at the time, I
didn't know that it was a bad idea :( If you do a trace to the servers,
you'll see a packet loss between 200.46.204.1 and the server itself that
just *shouldn't* be there. Apparently, on an unmanaged switch, if you try
and hard code the ethernet on the server to 100baseT/full duplex, the
switch, for some *stupid* reason, will downgrade itself to half duplex, so
you get a whack of errors ... right now, as a result, we're running
half-duplex on the server(s), which, of course, results in high collisions
*sigh* We're ordering in a new managed Dell Procurve switch next week, to
get that issue fixed ...
As to the hardware support itself ... see my other email ...
>
> Sincerely,
>
> Joshua D. Drake
>
>
> Marius Andreiana wrote:
>> Confirming it, also the slowness. sql2pg developer wants to move it to
>> sourceforge so we can work easier on it.
>>
>
>
> --
> Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
> Postgresql support, programming shared hosting and dedicated hosting.
> +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
> Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
>
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
