ehehronn

I concur. This plugin is a resource hog with any significant amount of events.

The plugin implements multiple worst-case bad database practices that severely affect performance. When server-side caching isn’t properly throttling access to it, its impact on our otherwise stable systems is comparable to a worm infection or persistent DoS attack. These pages, including those with TEC calendar widgets, cause an excessive load on our databases due to inefficient table structures, missing indexes (causing table scans), and incorrectly chosen data types (VARCHAR[] rather than DATETIME). Query complexity increases proportionally to the size of the table (the total number of Event occurrences) due to VARCHAR-to-DATETIME typecasting in WHERE and table JOIN clause statements (each of which trigger additional full table scans to determine candidacy) and missing indexes on fields that are used as lookups (each of which trigger an additional full table scan, again, to determine selection candidacy).

The plugin is demonstrably inefficient and any requests for improvement to the plugin developers, inevitably results in a loose promise to fix it with no action.