The only real (and that's questionable) performance issue with a  
frameworked app is startup. Beyond that, since so much of the running  
code sits in persistent scopes, practically the whole application  
runs from memory... and they don't take up that much room. Beyond  
that, there's JVM tuning and CF tuning that will allows you to  
circumvent even most memory usage issues to the point that, unless  
there's a bug in either CF or the framework you're using that results  
in a memory leak... or there's a bug in your code or a poor design  
choice that are causing the issue. Every application I've ever seen  
run into performance or resource allocation (read: RAM) issues could  
be traced back to one of those 2 problems: Server tuning or bugs at  
some level in your server or development stack.

Now, if there are bugs in CF and you report them AND run them thru  
one of the various mechanisms out there (like a member of the Adobe  
Community Experts team, direct to Jason Delmore, thru Ben Forta,  
etc.) you'll often be able to get action on a critical bug almost  
immediately. If it's a bigger bug than that, they can help provide  
you a workaround... you're rarely left stuck and helpless. You just  
have to be proactive about tracking down a resource to help.

If, OTOH, the bug is in a framework, often you can, by joining the  
mailing lists, commenting on team blogs, etc., get action on a  
critical show-stopper bug almost immediately... these teams thrive on  
community feedback and testing and will almost always respond  
positively to a valid bug that includes steps to reproduce and any  
other results of your effort to find the bug. What's more, posting a  
question to the effect that your app is expressing Behavior X, Y, and  
Z, "has anyone heard of this before?" will often help you gain a  
shortcut to tracking down a known bug on your own.

And that brings us to bugs in your own app... and even there,  
involvement with the framework community (because bunches of us write  
bunches of apps) can help you end-run by giving suggestions and hints  
and tips... though I do have to say that the more you interact with  
the list, the more you balance your involved between asking and  
answering, the better off you'll be in that respect.

As for server tuning, this is a great resource for you because we  
have some of the best and brightest experts on said in the CF  
community right here... and, if you (again) interact with the list in  
a positive and contributory fashion, often you'll get hundreds, if  
not thousands, of dollars worth of advice and wisdom for the low, low  
price of responding to a few peoples' questions with something  
intelligent and helpful. People respect that, and they're willing to  
help the people they respect... yadda yadda yadda. I'm sure you don't  
need me to give you any further info on the politics of tech lists. ;)

As for your comments about caching... all I have to say is this:  
whether you're implementing your own caching system within your  
application or you're embedding cfquery in every page and using  
cachedwithin, or you're bundling all your JS and CSS into files you  
reference in every <head /> block in your HTML... caching speeds  
things up. There's caching occurring at nearly every level in the  
server, from the OS to the browser, and it's no band-aid... it's a  
tried and true method if accelerating the performance of pretty much  
every aspect of your computer's operation.

What it all really comes down to is knowing what you're doing and,  
more importantly, knowing why you're doing it... faulty understanding  
can be fixed, but faulty motivations are far harder to dislodge and  
have a very far-reaching negative effect on your perceptions of  
everything in whichever space you're working. I congratulate you,  
therefore, on asking a question like this, but I'll really respect  
you based on the way you react to the information that people are  
providing you. Not that my respect is anything to write home about,  
but it's nice to be respected, especially when you're a craftsman in  
an intricate and important trade like ours. Respect is the currency  
which we use to trade answers and information in this world... so it  
really _is_ valuable, at least on some level.

In any case, I look forward your response...

Laterz,
J

PS - Ever developer I know uses a mix of frameworks to one degree or  
another, and often a mix of up to a dozen if you look at everything  
from the UI all the way back to the model and persistence layers.


On Oct 2, 2008, at 2:48 PM, Jon Hall wrote:

>
> Every direction I seem to go in my OO training,  many suggest
> frameworks as resolutions to my problems or ways to make it easier for
> me to develop.  What is some of the cost to these frameworks as far as
> performance? Alot of developers seem to use "caching" as a resolution
> to the performance costs, but isn't this just a band-aid to the real
> problem? Alot of people run their apps on VPS's and shared hosting so
> throwing more RAM & CPU at it can't be done easily, and you can only
> upgrade so far before the cost of upgrading outweighs trimming some
> fat out of the code.
>
> I read about people refactoring systems into OO Design from procedural
> and seeing a big performance hit.  Sure it was easy and fast with MVC/
> ORM/IC, but at what cost?  Do alot of developers use a mix of
> frameworks depending on the application need?  A data reporting system
> would benefit from MVC, but due to its simplicity would ORM be
> overkill or is the overhead minimal making it worth while?
>
> Jon

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CFCDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cfcdev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to