Comments (11)
If you don’t need EssentialsX to do anything, why use EssentialsX? What exactly are you using essx for if you’re not saving userdata.
from essentials.
If you don’t need EssentialsX to do anything, why use EssentialsX? What exactly are you using essx for if you’re not saving userdata.
In my setup, nearly everything that the plugin saves in these yaml files are just there for no reason. We use EssX for the command palette, not for jail, nor muting or banning players, etc. The problem with just removing the plugin alltogether is that Essentials is so common among staff members it is almost muscle memory so losing these would be inconvinient. I know that Essentials supposed to be a '"one plugin does it all" system when it comes to most server functions but it I think it was never meant to be used on server networks it is more like a "single server, all important functions" type of plugin. But it was adopted by many networks anyway.
from essentials.
Not an EssX dev here, just thinking. How big is your userdata folder, that you're worried about space? Similarly, IO should be tiny on this. It feels, at first glance, like this is microoptimization.
from essentials.
I'm not opposed to this option on principle, but I also don't see much of a compelling reason for us to support this. EssentialsX stores very minimal data on disk and does almost no reads/writes unless you use features that persist data (jails, homes, mutes etc). Any change to disable creating userdata files would require thorough testing, as this may have unforeseen consequences for commands that do expect persistent data.
from essentials.
Not an EssX dev here, just thinking. How big is your userdata folder, that you're worried about space? Similarly, IO should be tiny on this. It feels, at first glance, like this is microoptimization.
Currently the server in question is in development so not that big for now but imagine a network with let's say 1000+ players and Essentials is installed on every backend paper server so it creates a yml per player and per server for each and every one of them.. To me, that somehow sounds terrifying
from essentials.
Just Google Chrome has over 30 000 individual files stored in my AppData folder! None of this feels concerning. :)
from essentials.
I like the simplicity of having yaml files, however, I do support the idea of essentialsX being able to store user data in a mysql database (optional, ofc - could be a config setting) <3
from essentials.
I like the simplicity of having yaml files, however, I do support the idea of essentialsX being able to store user data in a mysql database (optional, ofc - could be a config setting) <3
MySQL is not relevant to this issue. See #1265
from essentials.
I like the simplicity of having yaml files, however, I do support the idea of essentialsX being able to store user data in a mysql database (optional, ofc - could be a config setting) <3
Yes yml is simple because you can edit things by hand easily but when you have a dozen players and multiple servers, this simplicity becomes pointless. I think Yml was never intended to be a data store, it was created for configuration.
from essentials.
I like the simplicity of having yaml files, however, I do support the idea of essentialsX being able to store user data in a mysql database (optional, ofc - could be a config setting) <3
MySQL is not relevant to this issue. See #1265
Ok, didn't know MySql was flat-out rejected 8+ years ago.. Duh, silly me. :) However, a database would be relevant to this issue regarding disk i/o ..
Reduced Seek Time: Databases are optimized for storing and retrieving data efficiently. They employ techniques to group related data together on the disk, minimizing the time it takes for the disk head to locate the desired information (seek time). With separate YAML files, the disk head would need to jump around a lot more to find specific user data.
Caching: Databases often cache frequently accessed data in memory, allowing for much faster retrieval compared to constantly reading from disk. This caching becomes less effective with scattered YAML files.
Batching: Databases can handle multiple read/write operations in a single batch, reducing the overall number of disk accesses needed. With YAML files, each user data access would require a separate disk operation.
Data Organization: Databases are designed for structured data, allowing for efficient querying and filtering. YAML files wouldn't offer the same level of organization and searching capabilities.
from essentials.
If I understand correctly, EssX uses yml more like a backup so some state and location data could be restored upon next server startup. To me, this sounds like Essentials reinvented Redis with persistence :)
from essentials.
Related Issues (20)
- The EssentialsXSpawn API provides no means of determining where a player will respawn. HOT 2
- If "respawn-at-home-bed" and "respawn-at-home" are set to true in the EssentialsX config, "respawn-at-anchor" is ultimately ignored.
- Currency won't be changed even IF I change it in the config.yml file HOT 12
- When I use the plugin version after the 2.21.0-dev+35-d4ecfd2, an error occurred while enabling Essentials
- Socialspy prefix colour formatting is missing the less-than symbol HOT 3
- Give command borks out with Error if player is not online HOT 3
- /skull gives a head item with wrong metadata. The skull does not apply the skin
- /nick should ignore color codes for nick character limit HOT 2
- Global command cooldowns
- world-change-fly-reset does not detect end portal use HOT 4
- Adding houses HOT 5
- Wrong color code format in Essentials messages HOT 5
- jail player list
- Add the clearenderchest and clearenderchestconfirm commands.
- Add the "Crafter" team. HOT 1
- Command Description & Usage strings do not respect per-player-locale
- `/kill` doesn't call `minecraft:entity_hurt_player` advancement trigger (breaking data packs) HOT 1
- custom join/leaves messages not work HOT 1
- Home Messages in chat not correct for de HOT 2
- make a new command HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from essentials.