2021-10-29, 17:42:24
There is no API in GetSimple lol, not object-oriented, just a bunch of global functions.
Well, we should be really careful when we say that with a certain number of pages, an XML application is faster than one that uses relational database. There are just too many factors to take into consideration. I mean, you can write a database-based application that is slower than one that reads the same amount of data from an XML file, or you can write a flat-file application that is much slower than the one that uses a database.
The number of pages plays only a subordinate role. Much more important is the amount of data and the data structure to be handled. A page can have different amount of bytes, the XML file can also have very nested complex structure. For example, a page may contain only a string "Hello world", another may contain huge text the length of a thick book etc. So, in general, to say that above a certain number of pages the application is no longer efficient is wrong. – It depends on the structure of the data, server configuration e.g. caching type, database connection pooling, quality of the code base and of course the query involved.
Yeah, if an XML file is small and the data structure is simple, and you just do a simple parse request, the script might be faster, but only slightly and only maybe. So little faster that it's hardly worth mentioning, I guarantee you won't notice. The entire JavaScript, CSS loading excess in the frontend is definitely a bigger bottleneck. Besides, a next slightly more complex MySQL query (for example to map a navigation structure with a counting of pages), makes everything bet again. Furthermore, the loading speed of the website is highly dependent on the concurrent requests (number of visitors). Again, this only applies if no cache engine is used - which no modern website should do. If the same cache engine is used in an XML and a database application, both can render the same content at the same speed. As far as I can remember (maybe I'm wrong), GetSimple caches its content in the frontend, but not in the backend when rendering the page list, which is why you probably notice the difference in loading speed.
Remember though, performance alone should not be a reason for choosing XML over the relational database, this is ridiculous.
Well, we should be really careful when we say that with a certain number of pages, an XML application is faster than one that uses relational database. There are just too many factors to take into consideration. I mean, you can write a database-based application that is slower than one that reads the same amount of data from an XML file, or you can write a flat-file application that is much slower than the one that uses a database.
The number of pages plays only a subordinate role. Much more important is the amount of data and the data structure to be handled. A page can have different amount of bytes, the XML file can also have very nested complex structure. For example, a page may contain only a string "Hello world", another may contain huge text the length of a thick book etc. So, in general, to say that above a certain number of pages the application is no longer efficient is wrong. – It depends on the structure of the data, server configuration e.g. caching type, database connection pooling, quality of the code base and of course the query involved.
Yeah, if an XML file is small and the data structure is simple, and you just do a simple parse request, the script might be faster, but only slightly and only maybe. So little faster that it's hardly worth mentioning, I guarantee you won't notice. The entire JavaScript, CSS loading excess in the frontend is definitely a bigger bottleneck. Besides, a next slightly more complex MySQL query (for example to map a navigation structure with a counting of pages), makes everything bet again. Furthermore, the loading speed of the website is highly dependent on the concurrent requests (number of visitors). Again, this only applies if no cache engine is used - which no modern website should do. If the same cache engine is used in an XML and a database application, both can render the same content at the same speed. As far as I can remember (maybe I'm wrong), GetSimple caches its content in the frontend, but not in the backend when rendering the page list, which is why you probably notice the difference in loading speed.
Remember though, performance alone should not be a reason for choosing XML over the relational database, this is ridiculous.