Plugins known to cause lag?

@Resistance This is the best answer to all of the lag issues. I used to have warnings for all my plugins till I invented into a dedicated box.

 

A dedicated box is always the best option for any game server I have used many myself in the past

 

Not at all, that's a rather silly comment to make, you know nothing about the hosting environment, at all.

And for your information, it's incorrect. The server I'm using is a Dedicated OVH box with an i5 3570k running one rust server and one Out of Reach Server.

The CPU usage seldom peaks above 15-20% and it sure as hell has never hit anything over 30% unless I'm on there doing something, like installing updates etc.

The rubber banding and pauses have gone since removing the plugin.

 

Its not a silly comment at all? I had a vps and would get horrific lag even though the specs were up to par. I was just saying in my experience a dedicated box fixed all my problems.

 

No VPS ever, will suffice.

It's not even legit dedicated CPU and the RAM space is there but the bandwidth you get depends on what else is going off, same with HDD. . It sounds like you should get a little more experience behind you before you start releasing comments like that.

 

I have been running a dedicated box for 25+ years I know what I am talking about and for a teen to think they know what they are talking about makes me laugh and you like a fool

 

I doubt you're beyond 25 years yourself. I'm 33 so yet again you're wrong... Common issue for you eh.

Please continue, this is proving me and I guess others with much amusement.

And I said hosting environment as in mine, you seemed to take that personally, which adds more amusement.

 

I am 45

 

I always am but some here seem to take it personal

 

I'll just add my two cents to this as well.
Door Share does a lot of file I/O, namely keeping track of doors and door owners.
This sort of file I/O is run when doors or locks are deployed. This can be very slow, as Oxide has to save the entire data file.
Basically, every time a door or a lock is deployed, data for every door is saved to the disk, which may be a lot (unless Oxide does some flush cache magic, no idea).
When opening doors, the plugin iterates through all that data multiple times, which may also be a lot for a large server with lots of entities, but probably isn't as bad as file I/O (occurs a lot more often, though). Combined with cache misses, because this is Lua we're talking about, it's likely that this is also fairly slow.
Either way, the plugin is incredibly inefficient and it's very likely that it's causing lag.

On the matter of distributed vs dedicated servers, distributed systems are hard. The kind of resource that's distributed (be it bandwith, CPU power, RAM, storage) doesn't really matter - there are hidden costs involved for each and every one of those.
For high performance systems you want everything to be local and reduce distribution as much as possible. The Rust server is a high performance system.
Web servers can easily be distributed - but even then, single requests are often handled locally without distribution, meaning the impact of distribution is minor and rather takes the roll of load balancing.
Regarding the plugin issue: Distributed CPU power, RAM or storage will all greatly worsen the inefficiency of this plugin.

 

Hey, finally someone who looked at the plugin which I bet took a whole 2 minutes, I'm sure that was much easier than flaming over some VPS nonsense.

 

Yeah, well, it could've been the case that Oxide still has a wrapper for save calls that buffers data file writes and only flushes every once in a while to reduce potential overhead caused by plugins like this.
Then again, this trades data integrity on server crash for performance, which may not be good since most people use CTRL+C to kill their server.