I would hazard a guess it has something to do with the layout you're referencing and/or the size of the found set (have you dumped the returned data and size of it?) Was this layout created specifically for use by CWP? Does it contain *only* the fields you absolutely need? If it has portals or summary fields you're going to slow things down. If you're using a layout not created just for CWP, try creating one and see what difference it makes.
Something else to look at is the fields you're finding on - are they indexed?
Fields are indexed.
Layout is not specific for CWP. I will give that a try and see how it goes.
had this once... the layout we picked for cwp actions (by error!) was one of a TO with a couple of 100'000 records..
The particular table has only 5000 records or so. Hopefully fewer fields on the layout will help.
Made a special layout for CWP and it is so much faster, just over 1 second. Threw all the compiled all the php files into OPCache and that shaved a few ms more off the process time.
How does CWP work with CDN or other caching?
Decent info. The PHP form builder is a very useful tool. Was that distributed at DevCon?
Likely. But the points about speeding up CWP, I've been preaching since there has been CWP.
Remember that a web server is best at serving FILES (of all kinds). If you can push off to caches that helps.
Also lean & mean layouts with as few calculated fields as possible.
Let PHP do the heavy lifting and leave fm scripting out of it.
So many ways to give you faster sites regardless of the db in the mix.
-- sent from myPhone --