Re: How Can I Help Make PM Faster?
by moritz (Cardinal) on Aug 22, 2008 at 17:11 UTC
|
Wait.
Really.
Our gods are working on it. They have new hardware, and working on the migration.
(It's not the engine that is slow, it's probably a bad mysql setup on freebsd or something). | [reply] |
|
|
| [reply] |
|
|
I can't really point you to a reference, I picked it in the chatterbox.
| [reply] |
Re: How Can I Help Make PM Faster?
by roboticus (Chancellor) on Aug 22, 2008 at 19:17 UTC
|
frogpile:
There was an interesting blog series by Krommatik that described some improvements. Even though you may want to wait for the hardware upgrade, you might be interested in reading the blogs, downloading the code, and start experimenting.
...rebooticus
I really need to edit my spelling checker's dictionary! :^) | [reply] |
|
|
I just happen to have links to those articles
Refactoring Everything, Day 01
Refactoring Everything, Day 02
Refactoring Everything, Day 03
Refactoring Everything, Day 04
Refactoring Everything, Day 05
Refactoring Everything, Day 06
Refactoring Everything, Day 07
Refactoring Everything, Day 08
Refactoring Everything, Day 09
Refactoring Everything, Day 10
Refactoring Everything, Day 11
Refactoring Everything, Day 12
Refactoring Everything, Day 13
Refactoring Everything, Day 14
Refactoring Everything, Day 15
Refactoring Everything, Day 16
Refactoring Everything, Day 17
Refactoring Everything, Day 18
Refactoring Everything, Day 19
Refactoring Everything, Day 20
Refactoring Everything, Day 21
Refactoring Everything, Day 22
Refactoring Everything, Day 23
Refactoring Everything, Day 24
Refactoring Everything, Day 25
Refactoring Everything, Day 26
Refactoring Everything, Day 27
Refactoring Everything, Day 28
Refactoring Everything, Day 29
Refactoring Everything, Day 30
Refactoring Everything, Retrospective
I just hope I've converted them properly (I checked some, but not all)
| [reply] |
|
|
| [reply] |
Re: How Can I Help Make PM Faster?
by cbrandtbuffalo (Deacon) on Aug 22, 2008 at 17:16 UTC
|
I think the comments regarding the hardware are a bit dated since right now the current hardware is itself a bit dated. There are efforts under way right now to migrate to new hardware and we should see a performance jump then.
Another thought has been to add some javascripty functionality similar to slashdot and use.perl.org to cut down on the full page loads the server has to do for comments, etc.
See also this thread: Re: Could PerlMonks use some cash? | [reply] |
|
|
I've wondered for a long time why voting uses a full page reload rather than Ajax.
| [reply] |
|
|
| [reply] |
|
|
| [reply] |
|
|
|
|
|
|
Re: How Can I Help Make PM Faster?
by Tanktalus (Canon) on Aug 22, 2008 at 17:15 UTC
|
Well, let's see. You could write your own CB client. You could write a bot to monitor CB and/or private messages and respond to them. You could create more stats based on the CB or XP, and publish them to another website. All of these should help keep critical information in the database cache, and thus make everything faster for everyone.
*ahem*
(sorry.)
| [reply] |
Re: How Can I Help Make PM Faster?
by dHarry (Abbot) on Aug 23, 2008 at 14:52 UTC
|
| [reply] |
|
|
That sounds like a good idea in general, but read tye's node Re: Could PerlMonks use some cash? (naw) over in the thread Could PerlMonks use some cash?.
As I read that, PM basically has funds more than adequate for its present situation. A great deal of funds would be necessary to have much of an impact at this point. I'm sure there would be a specific plea if there's a specific need.
If anyone wants to add to PM's rainy day fund, I wouldn't discourage it. I'd probably take tye's advice for now, though, and donate any money I was going to donate to a Perl cause to something which needs the funds more immediately.
| [reply] |
Re: How Can I Help Make PM Faster?
by repellent (Priest) on Aug 23, 2008 at 03:00 UTC
|
Phew! I thought it was just me noticing slowdowns from time to time.
In the meantime, is there anything recommended that I can do to my "Settings Nodelet" to speed things up?
Thanks. | [reply] |