vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Does anyone have a copy of the post (or whole "Chiron's new system" thread) from late 2001/early 2002 where Chiron goes into details on how he optimized his new system? Tried searching Google Groups but it seems Chiron was using the no archive flag back then. I got a partial threads from Google (message IDs 20020101085320.3bac52c8.mbowles@satx.rr.com and iksk3ug10batk2qmq1el9phjlicapkph57@4ax.com) which had some interesting tidbits, but not with any of Chiron's posts. Even tried looking up the reference message IDs in those starting messages, but all that got me to was "not found" (which would be consistent with no archive flag set) and another thread. I also found a thread by Jurgen mentioning that thread (message ID 3C90F622.4010700@pophost.eunet.be) and another by buck that seems to be quoting an uncached reply to Jurgen's post (message ID pfd7bu43cem7efis1gl12oe0qrcpc0bsh0@4ax.com). Those had a few more interesting tidbits, but I was hoping someone still had a copy of the full thing. Reason I ask is I need to optimize a PII 450 system for Slackware 10 because a single MUD process is chewing up 40% of the CPU with very low memory load, which is just odd as usually LPMUD drivers are memory hogs, not CPU ones. Already tried recompiling the driver with -O4 and -march=pentium2, which yielded a moderate improvement in "snappiness" but there's still the steady march to 40% cpu on ps output along with a steady increase in processing lag for the process itself. This machine is also my Internet workstation at home (typically using X w/ Fluxbox, Mozilla, several terminals) due to certain restrictions in my ISP contract (such as the large fine if one is caught sharing a connection between multiple machines) so getting the CPU issue under control is a priority. There didn't seem to be such issues using the old 8.1 (with server upgrades) install that was on the machine previously, but recompiling for security fixes was getting rather tedious and CPU taxing as well. I'm wondering if the issue could be helped by optimizing the dynamically linked libraries that the MUD driver uses. Searching Google Groups for things like gcc and optimize/optimization, seems many times someone asks about optimizing, they are pointed back to Chiron's post. Unfortunately, it does not seem to be present in their archives. I've spent several hours looking, even going down to just browsing in the target date range of Dec 2001-Mar 2002. So if anyone has it and is willing to email it to me, you should find a routable email address by digging into the headers of this post. |
| |||
| -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In alt.os.linux.slackware, Cichlidiot dared to utter, > it seems > Chiron was using the no archive flag back then. Yes he was, and this is a good reason why that flag is bad. > Those had a few more > interesting tidbits, but I was hoping someone still had a copy of the full > thing. This isn't the whole thing, but... Message-ID: <slrnatamfk.fnb.Chiron_Files@raven.home> > due to certain restrictions in my ISP contract (such as > the large fine if one is caught sharing a connection between multiple > machines) Use OpenBSD's pf and the modulate state and scrub options for better hiding NAT. > So if anyone has > it and is willing to email it to me, you should find a routable email > address by digging into the headers of this post. Better yet, post it here so that it is better archived this time. :^) - -- It is better to hear the rebuke of the wise, Than for a man to hear the song of fools. Ecclesiastes 7:5 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBQHVLlKR45I6cfKARAqb6AJwLFtezt832BwQglCJDaQ 816h0nowCgsrN0 zgBBJoUuKVNOoX/aeZ/FDFI= =cdFo -----END PGP SIGNATURE----- |
| |||
| NOTE: This message was sent thru a mail2news gateway. No effort was made to verify the identity of the sender. -------------------------------------------------------- pgp trash troll delete Hicks, Alan 188 Shady Dale Dr Lizella, GA 31052 478-935-8132 +Alan Hicks+ <alan@lizella.network> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > In alt.os.linux.slackware, Cichlidiot dared to utter, > > it seems > > Chiron was using the no archive flag back then. > Yes he was, and this is a good reason why that flag is bad. > > Those had a few more > > interesting tidbits, but I was hoping someone still had a copy of the full > > thing. > This isn't the whole thing, but... > Message-ID: <slrnatamfk.fnb.Chiron_Files@raven.home> > > due to certain restrictions in my ISP contract (such as > > the large fine if one is caught sharing a connection between multiple > > machines) > Use OpenBSD's pf and the modulate state and scrub options for better hiding > NAT. > > So if anyone has > > it and is willing to email it to me, you should find a routable email > > address by digging into the headers of this post. > Better yet, post it here so that it is better archived this time. :^) > - -- > It is better to hear the rebuke of the wise, > Than for a man to hear the song of fools. > Ecclesiastes 7:5 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.1 (GNU/Linux) > iD8DBQFBQHVLlKR45I6cfKARAqb6AJwLFtezt832BwQglCJDaQ 816h0nowCgsrN0 > zgBBJoUuKVNOoX/aeZ/FDFI= > =cdFo > -----END PGP SIGNATURE----- |
| |||
| +Alan Hicks+ <alan@lizella.netWORK> wrote: > > Yes he was, and this is a good reason why that flag is bad. > It is probably good for those posts that simply say STFW because those won't contribute anything to the google archive. - Kurt |
| |||
| ~kurt <actinouranium@netscape.net> wrote: > +Alan Hicks+ <alan@lizella.netWORK> wrote: > > > > Yes he was, and this is a good reason why that flag is bad. > > > It is probably good for those posts that simply say STFW because > those won't contribute anything to the google archive. And that would take care of about 99.9% of -Cibahole-'s postings. cordially, as always, rm |
| |||
| ~kurt <actinouranium@netscape.net> wrote: > +Alan Hicks+ <alan@lizella.netWORK> wrote: >> >> Yes he was, and this is a good reason why that flag is bad. >> > It is probably good for those posts that simply say STFW because > those won't contribute anything to the google archive. One would have expected by the tone and content of this post, that above referenced poster would have put said flag into the header. Particularly since the content of the post only encourages certain other noise. One would assume wrong however. Please stick to the topic. If you don't have a copy of the optimization post, move on along even if you didn't much care for Chiron. He did contribute, and this was one of the contributions. And as far as BOFHs go, he was mild and polite compared to a few I have run across. One of them would have a veritable field day with some of you until he bored of the repetition (the word "chew toy" comes to mind). |
| |||
| Cichlidiot <fishlover@nospam.invalid> wrote: > > One would have expected by the tone and content of this post, that above > referenced poster would have put said flag into the header. Particularly Good point - to some extent. However, I'm not going to add the no archive header for every off topic post that I take part in. > Please stick to the topic. If you don't have a copy of the optimization > post, move on along even if you didn't much care for Chiron. He did I wasn't refering to +Chiron+. Just an observation from a few years ago when someone mentioned doing a google search for something on this newsgroup and only coming up with STFW replies. I don't think +Chiron+ was *ever* able to stick to simply saing STFW or GAFC. Usually, he was able to drag a simple "Fuck You" out into 80 or more lines of text. I think there is even a mod quote about that aspect of his writing style. > contribute, and this was one of the contributions. And as far as BOFHs go, > he was mild and polite compared to a few I have run across. One of them > would have a veritable field day with some of you until he bored of the > repetition (the word "chew toy" comes to mind). I'm not sure what you point is? Are you complaining about the thinned skinned people in this newsgroup who get too easily offended? Not my concern other than their occasional whining. - Kurt |
| |||
| NOTE: This message was sent thru a mail2news gateway. No effort was made to verify the identity of the sender. -------------------------------------------------------- pathetic loser trash troll delete -- Roger Maynard is a Pathetic loser! Killfile all posts that end with "cordially, as always"! |
| |||
| Ralph Malph wrote: > ~kurt <actinouranium@netscape.net> wrote: > > +Alan Hicks+ <alan@lizella.netWORK> wrote: > > > > > > Yes he was, and this is a good reason why that flag is bad. > > > > > > It is probably good for those posts that simply say STFW because > > those won't contribute anything to the google archive. > > And that would take care of about 99.9% of Roger Maynard's postings. > > cordially, as always, > > rm -- pathetic loser trash troll delete -- Roger Maynard is a Pathetic loser! Killfile all posts that end with "cordially, as always"! |
| ||||
| NOTE: This message was sent thru a mail2news gateway. No effort was made to verify the identity of the sender. -------------------------------------------------------- NeoSadist is a pathetic loser <NeoSadist_is_a_pathetic_loser@justlinux.ca> wrote: > Ralph Malph wrote: > > ~kurt <actinouranium@netscape.net> wrote: > > > +Alan Hicks+ <alan@lizella.netWORK> wrote: > > > > > > > > Yes he was, and this is a good reason why that flag is bad. > > > > > > > > > It is probably good for those posts that simply say STFW because > > > those won't contribute anything to the google archive. > > > > And that would take care of about 99.9% of NeoSadist's postings. > > > > cordially, as always, > > > > rm |