Thanks for that, I tried google but most of it was in fancy words I didn't understand

Dave +1

this is the event as is, we do not recommend to bind to it as this will break the whole website, as it is strictly used within the certain parts of the software functionality only. 

in the database there i think 2 cache  tables db cache etc  that are not being used 
the tables are empty why 

Guys, the method which Love Oxwall mentioned has been used before. We have used it to cache the queries. But in the process of development we have found out that it is very complicated to create the system which caches all queries.

The fact is that the conditions for storage and output information are different and depend on plugins' data. And the main issue was inability to develop the base  algorithm which can synchronize data and keep the data integrity. That is why we have abandoned this system.
Nonetheless, some plugins require to cache the queries, so we have implemented simple queries caching system. For example, you can see how this system works in the Newsfeed plugin.

To explain it in a simple way , let's take as a sample the query of selecting all on-line users. Every time when you open the on-line users page, the following query runs:

SELECT * FROM `ow_base_user_online`

And you receive the query result. To optimize this process we can save the result data in the special cache table and then next time when you open the on-line users page, the system will grab the saved result from cache table instead of running the query again.

So, that is how the cache system can be used in our software.
If you need to implement the queries cache system in your own plugin, then implementing such kind of functionality will be most optimal.

Despite the fact that the development of the system that caches all queries has not been completed, we  believe that this kind of functionality is necessary for our software. That is why we  still consider this system development. But it is  very complicated process and it will take pretty much time.

it's not getting easier when mixing up the terms request/response (which usually mean HTTP-Request / HTML-Response) and query/result set (usually used for fetching data from db 

the whole way oxwall drives the database needs a rethink and change so it works with mod security 

all other database driven scripts can run with mod security no problems 

and i have speed plugin that shows db hits and misses and it is showing lots of database misses and is growing fast 

Heri Bender, thank you for paying attention to an error in terms. I have corrected my post.

Tammy, could you please specify what challenges have you encountered while working with our database and the mod_security settings. What errors did you get? Please provide us with the detailed steps to reproduce them.
Tammy, as we always said, to solve the issue first of all, we need to reproduce it.
Unfortunately, there is no useful information for us in yours report. If you want us to assist you to solve the issue, it will be good to provide us with more details about issue you have faced: the DB queries log, the speed plugin statistics etc.

install mod security on your server and turn it on

every action on site  mod security thinks is sql injection or breaks other rules and blocks that person ip addy from the server 

you have to whitelist heaps of rules so you and members dont get blocked from the server  and having these rules opens the server to be hit 

the db misses i think are from chat sometime on open chat it misses the info and you just get spinning wheel
console notifications sometimes say you have 5 new and on open drop down you get blank
box no spinning wheel missed get info and that has happened on oxwall to me twice as well
same for friend request 
everything else seams to be fine 

speed optimizer page

Tammy, all the matter is that the mod_security module on your server considers that some actions like the Ajax requests are a threat to the server and block them. This is not the issue of our software or database this is the specificity of mod_security.

You need to change the configuration to make the checking not so strict as it is now. If you look at our server requirements, you'll see that the mod_security (strict configurations) should be off. We ask to disable mod_security module completely, because we do not provide instructions on server configuration. However if you need the server techs should be able to disable some settings of the mod_security module in order to make the feature work on the website and still have the module ON.

all other scripts work with mod security fine no problems 

but oxwall i have had to whitelist over 50 rules 
and having so many rules white listed is a huge security risk 
its not just ajax requests its just about everything that is inserted into databass by the script 

for security reasons this should be looked at 
any server security feature that has to be turned off or whitelisted to run the script is a huge problem and should be addressed