Not signed in

Want to take part in these discussions? Sign in if you have an account, or apply for one below

Site Tag Cloud

Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.

• CommentRowNumber1.
• CommentAuthorTobyBartels
• CommentTimeJul 20th 2009

I want to make sure that people know that there is now a shortcut to restart Instiki, particularly convenient when (as right now) it's difficult to type more than 2 or 3 characters into the server at once.

Log in, and then type the command

~/x

That's it!

(Earlier I told some people to type ./x, but that only works if you're in the home directory when you log in, which is not necessarily the case!)

Twice now, I've done this where I was only able to get the ~ in and the terminal froze. So I killed that terminal, logged in again, and continued with /x. It worked! Before I created the script, it could take forever (sometimes effectively literally) to type /etc/init.d/lighttpd restart and /etc/init.d/instiki restart.

(Note that if the terminal freezes as you're entering a command, the first character after the last echoed character, that is the first character that did not get echoed back to you, did go in, so you should not type it again when you log in a second time.)

• CommentRowNumber2.
• CommentAuthorTobyBartels
• CommentTimeJul 24th 2009

Instiki was getting slow again, so I restarted it. (And I still can't get past the tilde the first time I log in, so I had to log in again to finish typing the command!)

My theory is that Instiki slows down over time as some sort of cruft develops; (I have no hypothesis as to what this cruft may be or how it might arise through some poor behaviour in Instiki itself or in the server that we have).

So when Recently Revised is called, it doesn't merely slow things down during the duration of the call; it also adds a lot of cruft and leaves things running more slowly afterwards. But normal usage will also add cruft over time. To clear the cruft, therefore, we still need to restart Instiki every once in a while.

• CommentRowNumber3.
• CommentAuthorUrs
• CommentTimeJul 24th 2009

I should say that I tried to "Export as Matrkup" a few minutes ago. It was already slow before. Then it got slower. (And the export didn't produce a file either. Didn't since sereveral weeks now).

I agree with your cruft theory, that's my impression, too.

I think we should install a script that restarts instiki automatically every hour or so. Can you do that?

• CommentRowNumber4.
• CommentAuthorTobyBartels
• CommentTimeJul 24th 2009

No, I can't do that, at least not yet; I could probably figure it out, but I'd have to read about cron jobs or something. (I also think that every hour is much more often than necessary; but then I'm not sure how much restarting interferes with usage.) On the other hand, if Andrew writes such a script, then I can probably figure out what it's doing and tweak it.

• CommentRowNumber5.
• CommentAuthorAndrew Stacey
• CommentTimeJul 24th 2009

Instiki already restarts itself twice a day (and logs how much memory it's been using just before the restart). It does this at 6am and 6pm, and it seems to be on UTC (so figure out your own timeshifts from that).

• CommentRowNumber6.
• CommentAuthorUrs
• CommentTimeJul 24th 2009

Okay, I see. I don't know, maybe four times a day would make sense?

• CommentRowNumber7.
• CommentAuthorTobyBartels
• CommentTimeJul 24th 2009

Ah, then that explains why it speeds up sometimes when I'm sure that I'm the only one using it (probably the AM restart) and I haven't restarted it!