From: "Michael A. Peters" on 24 Mar 2010 15:05 Tommy Pham wrote: > > The response time, max 5 seconds, will be tested on local gigabit LAN > to ensure the adequate response (optimized DB & code & proper > hardware) without worrying about users' connection limit and site's > upload bandwidth limit (which can easily rectify). Then thereafter > will be doing stress test of about 10 concurrent users. As for the > major queries, that's where threads come in, IMO, because those > queries depend on 1 primary parameter (category ID) and 1 secondary > parameter (language ID). This particular site starts with 500 > products about 15 categories, without many of those mentioned filters, > later grew to its current state. > I don't know about the proposed scenario you give. But I do know when my own site felt a little sluggish, I implemented APC and a cron job that preloads all the queries at the beginning of the day. Any changes to a table dump the cache and reload it. Site is now fast and the database is only pounded in the early AM cache preload (which may actually not even be necessary, but I do it just in case there are any scenarios where I change DB and forget to nuke cache for effected queries). If database is your bottleneck, APC (or other caching methods) is your friend.
From: Rene Veerman on 24 Mar 2010 15:16 On Wed, Mar 24, 2010 at 3:13 PM, Robert Cummings <robert(a)interjinn.com> wrote: > Rene Veerman wrote: >> >> talk to me about this some other time. >> >> atm i'm having an argument with per and his kind about their very very >> annoying behaviour of determining my toolset for me. >> keeping a thread on topic is also ettiquette from the mailinglist rules >> eh? >> >> you might wanna consider just how much it pisses me off to have strangers >> determining my toolset and/or lifestyle for me. >> that's why i got rude. no other reason. > > Umm... you or your boss/client chose PHP. That means one of those two > determined your toolset. Maybe next time you might want to pony up for a > requirements analysis to determine if the toolset is right for the job. > you've never heard of feature-creep, changing environments and requirements, etc?
From: Rene Veerman on 24 Mar 2010 15:22 On Wed, Mar 24, 2010 at 3:37 PM, Jochem Maas <jochem(a)iamjochem.com> wrote: > > Someone who respects you will buy you a sandwich if you need it. i'd rather build products that are useful enough to be sold, than to wait for anti-starvation handouts gained from respect. > > But seemingly you're only interested in leveraging other peoples time and > experience to further your own career, good luck with that around here. > i've spent quite a bit of time on this list writing replies of my own to other people's software problems here. in fact i think i've spent more time on other's problems for free than i've received back in useful tips. and i'm not bitching about that.
From: Robert Cummings on 24 Mar 2010 15:30 Rene Veerman wrote: > On Wed, Mar 24, 2010 at 3:13 PM, Robert Cummings <robert(a)interjinn.com> wrote: >> Rene Veerman wrote: >>> talk to me about this some other time. >>> >>> atm i'm having an argument with per and his kind about their very very >>> annoying behaviour of determining my toolset for me. >>> keeping a thread on topic is also ettiquette from the mailinglist rules >>> eh? >>> >>> you might wanna consider just how much it pisses me off to have strangers >>> determining my toolset and/or lifestyle for me. >>> that's why i got rude. no other reason. >> Umm... you or your boss/client chose PHP. That means one of those two >> determined your toolset. Maybe next time you might want to pony up for a >> requirements analysis to determine if the toolset is right for the job. >> > > you've never heard of feature-creep, changing environments and > requirements, etc? Not usually, at the level of the language choice, is an about turn done after a requirements analysis has been completed. Feature creep is a management issue. Cheers, Rob. -- http://www.interjinn.com Application and Templating Framework for PHP
From: Rene Veerman on 24 Mar 2010 15:24
On Wed, Mar 24, 2010 at 3:25 PM, Robert Cummings <robert(a)interjinn.com> wrote: > Rene Veerman wrote: >> >> php is not a hammer, its a programming language. > > It's hard to discuss anything with someone who doesn't comprehend a > metaphor. haha. "comprehend". you mean "accept". that metaphor is stretched to breaking point as far as i'm concerned. > >> one that i feel needs to stay ahead of the computing trend if it is to >> be considered a language for large scale applications. > > Personification of PHP doesn't make your argument any more salient. PHP > isn't trying to stay ahead of anything. People are using it to solve > problems, not to meet some phantom ideal of a "computing trend" threshold. > >> but you nay-sayers here have convinced me; i'll be shopping for >> another language with which to serve my applications and the weboutput >> they produce.. >> >> thanks for opening my eyes and telling to abandon ship in time. > > Obviously we didn't open your eyes. > Well excuse me for not dumping 50-100k lines of my own cms code instantly now that i realize that in order to scale it, i could really use features like threading and shared memory. |