3DSPlaza forums - Yet more Chatroom Optimisation

Back to forum: Announcements

Search forums via Google

0 Users appreciate this thread.

Yet more Chatroom Optimisation

Started by SomeLuigi
(2012-08-03 11:50:00)

SomeLuigi (2012-08-03 11:50:00)

After noticing that my latest bit of optimisation worked for a bit, but soon enough, 503s again!

But I'm not finished YET! Moar Moar Moar Optimisations!

I was thinking about this and realised this:

Most messages sent have nothing to do with commands, so why should the chat check every command individually?

Bad:

Invalid nesting error at tag #color (phase "color=(.+)") when parsing

[box=red]

[color=#FFFFFF]

IF command is /me

IF command is /ban

IF command id /warn

IF command is ....

[/color]

[/box]

### end of error report. extra information that may or may not be useful to developers: *IBV*color*OCTTWO*1*OCT*1*CCT*1*END OF EXTRA INFO*

Better:

Invalid nesting error at tag #color (phase "color=(.+)") when parsing

[box=lime]

[color=#FFFFFF]

IF message is a command, continue, otherwise stop

IF command is /me

IF command is /ban

IF command id /warn

IF command is ....

[/color]

[/box]

### end of error report. extra information that may or may not be useful to developers: *IBV*color*OCTTWO*1*OCT*1*CCT*1*END OF EXTRA INFO*

And whilst I go and mess with that, I'll show you a few "diagrams" to do with server overload:

There is a chance that some commands may break with this change, so those need to reported to me so I can investigate the problem further, and possibly fix it.

This optimisation task did go through 2.1 revisions, most of which I spent moving over blocks of code.

I cut 44.3 KB slack when sending a message not containing a command. You may not think that's much, but a message is sent at most every 3-5 seconds, making this an efficient optimisation.

Well, anyway, I'm going to publish this Thread out for everyone to see and move it out of the Void.