[Maypole] Re: Maypole responding to requests very slowly (or, how to get just one associated record instead of getting the world)

[Dave Howorth]

Brian Glass wrote:
>>>> I only use AsForm for non-relationship fields. It turned out
>>>> that the real performance problems were created by object
>>>> creation, not large queries or MySQL. This little tweak makes
>>>> my Maypole application very fast.
>> If people are interested or have ideas for improvements or better 
>> ways to do this I can flesh it out a little better. I would think 
>> this sort of thing would come in handy in the factory templates.

Simon Flack replied:
> Forgive me if I'm barking up the wrong tree here, but isn't this a 
> Class::DBI::AsForm issue? I seem to remember suggestions that setting
> the Essentials columns appropriately in your CDBI classes would give
> significant performance improvements. Have you tried that, and if so,
> did it help?

Isn't it more a case of TMTOWTDI? I think it's good to see different 
ways to approach a problem and certainly I've seen object creation be a 
killer before, so I'd like to know what Brian has done. But I'd also be 
interested in comparative numbers :)

> I was also under the impression that the default templates were just
> examples: 
> http://lists.netthink.co.uk/pipermail/maypole/2004-November/000975.html
> 
> I'd like to see them stay that way and not over-complicate them. If
> there is a demand for drop-in templates, I suggest creating Maypole
> separate "theme packs".

Perhaps it would be useful to evolve a 'Maypole template cookbook' like 
the request cookbook, that shows alternative techniques that can be used 
in particular situations within templates?

Cheers, Dave