Hi @draven666 — thank you for taking the time to bring this up. Yes, you are quite correct, there can be a lot of individual entries in wp_options table.
The plugin has was initially designed to use the native WordPress data handling to store settings for each page. This was when we estimated that the average site using our plugin would be about around 100 pages. Of course, we’re now seeing many WordPress websites over 500 pages, which can result in a lot of additional entries in the wp_options table, as you have identified.
That said, in our all of our testing, we found that individual entries were faster than loading one large data structure, and also easier on data management. In fact, when we tested installations of 500 – 2500 pages, we did not notice any significant decline in performance.
In the most recent update, we have also switched from auto-loading each of those entries, to requesting them on-demand, to further reduce the memory load.
In December, we started migrating much of our data into separate pegasaas-only database tables. The move to the data handling should be complete by the March “minor” update of 2.3.0.
Again, thank you for taking the time to bring this up — we can let you know when the version with the completely migrated data handling has been released.
