Jun 16, 2018 04:31 PM|uid390594|LINK
as I said, a database would be too slow. and databases are outdated. except for some really weird risky and still imperfect projects, that dont even have a fancy name. and require learning to use, and still nowhere near as fast. (im talking about delayless
im about to finish my project. The perfect .NET friendly, inmemory in-process Modeldatabase with categorytree support and submodels. including an model editor. and my website is faster than 99+% of the internet. Models can be provided as classes. and the
classes are automatically extended with Database record properties, such as ID's owners, creationtime etc. changing all models in the database does not even take more than 20 ms.
good bye SQL, goodbye entity framework, and good bye to cashing.
please look at my latest thread, where I ask about getting the variables from a class, to make my object editor.
ive based the inmemorycashe on the application variable anyhow, and added a background thread to save the data when requested. When any really important data is written that shouldn't be abruptively lost, it is written to a backup file in case the app doesnt
make it to the next save-tick. if you still have an idea for an out of process solution that is just as fast as a local variable, id like to know. how fast are memory mapped files? in a test ive done, it was too slow, but also it was a really bad demo project
ive downloaded about it. there was a 300 ms delay before the data was received. but I need it to be absolutely unmeasurably ~ 0.