Hi Joe et al,
My first step..
I would use a tool like https://errormator.com/ now, to determine what the
real issues are. You might be surprised or not. Then if a migration to
web2py is warranted I would use the same tool during development to
optimize the application and keep metrics as the us
I should add that one can always do
cache.ram('whetever',lambda: cache.ram.clear(), 5*60)
to clear all cache every 5 minutes. Clear also takes a regex and can be
used for partial cache clear.
cache.ram('whetever',lambda: cache.ram.clear(regex), 5*60)
cache.ram cannot clear cache automa
Back to scalability doubts. My experience in 3 points:
1. use a multiprocess, event server. Rocket is great for prototyping, bad
for concurrency.
2. never make assumptions on where the slow part is. Profile everything.
3. make indexes by hand on sql tables if needed.
For instance I was hit by au
Hi Joe Barnhart,
can you please tell me how much hosting costs per month for your app?
bandwidth, disk, etc.
thanks,
Alex Glaros
On Saturday, August 3, 2013 12:18:07 PM UTC-7, Joe Barnhart wrote:
>
> I'm not the OP, but I am also risking web2py on a "large" project...
>
> In my case I'm repla
Looks like using a memcache (which using finite memory) is the only way to
go in this case?
On Monday, August 5, 2013 6:42:09 AM UTC+8, Massimo Di Pierro wrote:
>
> If the query depends on user input than yes.
> select(cache=(...)) uses the SQL QUERY as key. If it is possible for the
> QUERY tha
>
> For example when you do
rows = db(query).select(cache=(cache.ram,3600),cacheable=True)
>
> Is there any way to specify the key, or to empty the cache after some time?
>
Not currently a way to specify the key, though I suppose we could add that
option. Here's the code that generates the key:
If the query depends on user input than yes.
select(cache=(...)) uses the SQL QUERY as key. If it is possible for the
QUERY that you are caching to always be different because depends on user
this input you have a memory leak. Actually more than that. You have a DoS
vulnerability because a user
My cousin is making a social network using web2py and he worked with Rails,
for example.
I'd use it, I think it has a clean and easy code. But that's up to you.
If you want to know what social network it is, http://tymr.com
Sexta-feira, 2 de Agosto de 2013 4:04:27 UTC+1, hello world escreveu:
>
Thank you Anthony.
Maybe I missed a point in the book, but does memory leak with cache.ram also
applies to select caching?
For example when you do
rows = db(query).select(cache=(cache.ram,3600),cacheable=True)
Is there any way to specify the key, or to empty the cache after some time?
What is
On Sunday, August 4, 2013 11:26:25 AM UTC-4, Loïc wrote:
> Hello Massimo
>
> Could you please elaborate the following sentence, and if possible give an
> example of what we should do/avoid?
>
> "built-in system is ok if you have one web2py instance and if you reuse
> the same keys else you can h
Hello Massimo
Could you please elaborate the following sentence, and if possible give an
example of what we should do/avoid?
"built-in system is ok if you have one web2py instance and if you reuse the
same keys else you can have a memory leak (keys do not expire with cache.ram)."
Thank you
--
To me there are three issues with scalability:
- database, it is always the bottle neck but there is no differencd between
web2py and rails in principle. They can use the same database architecture.
- filesystem. web2py by default uses the filesystem more than rails (to
store sessions for example
I'm not the OP, but I am also risking web2py on a "large" project...
In my case I'm replacing a Rails site that services about 15,000 customers
and has a variable workload -- about 5000 users compete for time on the
site every week. It has a database size of about 20GB of small records
(~1K ea
i service about 25 requests per second average 24 hours a day on google app
engine. perhaps that's only considered medium size these days, but it's
running pretty well.
cfh
On Friday, August 2, 2013 2:46:31 PM UTC-7, Aurelio Tinio wrote:
>
> Curious to hear, what do you consider large scale?
>
Curious to hear, what do you consider large scale?
The more detailed you are about your project the better the response the
community can provide.
Fwiw, having only worked with web2py since the beginning of the year I've
been contemplating similar questions too and essentially the answer is... *
15 matches
Mail list logo
