There are lots of easy ways to optimize for scaling up. Spend your energy
on end user functionality until you run into issues.
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list
Only if you're using conditional models.
-Jim
On Thursday, July 20, 2017 at 6:00:45 PM UTC-5, Alex Glaros wrote:
>
> any performance advantage to moving controller files out of default.py
> into their own file?
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- htt
any performance advantage to moving controller files out of default.py into
their own file?
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received
On Thursday, July 20, 2017 at 2:45:09 PM UTC-4, Alex Glaros wrote:
> Jim, regarding "That said, if you've got 500 tables in your app, you probably
> don't want to use the web2py default table instantiation on every request."
>
>
> 1. did you mean to put db.py model tables into categorized sub ta
Yes, the goal is to only load the table definitions that you need.
http://web2py.com/books/default/chapter/29/04#markmin_conditional_models
we use a form of conditional models along with lazy tables ->
http://web2py.com/books/default/chapter/29/06/the-database-abstraction-layer#Lazy-Tables--a-maj
Jim, regarding "That said, if you've got 500 tables in your app, you
probably don't want to use the web2py default table instantiation on every
request."
1. did you mean to put db.py model tables into categorized sub tables -
e.g., accounting_related_tables.py, email_related_tables.py,
invento
Our redis server only has 8GB of ram. We load balance primarily for
redundancy, not load. We only have about 100 users actively using our
system. It is an internal app for our business.
-Jim
On Thu, Jul 20, 2017 at 11:46 AM, Chinh Dang wrote:
> Our app starts small maybe around 50 tables max
Our app starts small maybe around 50 tables max, but may grow as more
features are being added. Planning to use load balancing and failover.
Since you use redis, can you give me a ballpark on the memory usage for the
amount of traffic you have? My concern is when the redis host runs out of
memory.
My philosophy is to not optimize until you need to.
That said, if you've got 500 tables in your app, you probably don't want to
use the web2py default table instantiation on every request.
Any idea what you're traffic will be like? Are you going to load balance?
Our main app has over 150 tab
9 matches
Mail list logo
