Yes you can soft link however when you get to the point of multiple servers and upgrading code on each it is a pain.
The site I`m working in is very large. I am now rewriting the code with a new technique in modules and using conditional if statements in side each module so you have 100% control of what loads when and where. I should have the new code live soon and will follow up if there was a huge improvement or not. Locally I have seen a huge improvement on one page the loading time went from 0.128 to 0.045 seconds and a functioin call drop from 85845 to 31380 calls and this example is from a page with a single query to a single record in the db. You can imagine the improvement on a complicated page. On May 27, 2012 8:56 AM, "Cliff Kachinske" <cjk...@gmail.com> wrote: > Yes, you can soft link individual files within the file system. You can > even rename the target files so the tables load in the right order. > > It will work on Linux and OS-X and should work on all unix flavors. > > On Friday, May 25, 2012 3:25:37 PM UTC-4, David McKeone wrote: >> >> Cliff, >> >> Certainly an interesting idea. I'm assuming that you mean soft-linking >> the file system? Would that work on Windows (I have to be able to deploy to >> Windows and Mac)? >> >> -David >> >> On Friday, May 25, 2012 8:05:06 PM UTC+1, Cliff Kachinske wrote: >>> >>> Maybe you could soft link the model files. >>> >>> For controller foo you would have a file models/foo/foo.py >>> >>> If controller bar needs needs data from table foo, you would create a >>> soft link in you models/bar directory to models/foo/foo.py. >>> >>> Note if you link it in as foo.py, it will run after bar.py, so you would >>> want to name the link according to the necessary sequence. >>> >>> Don't know what this would do for migrations on the production box, >>> though. >>> >>> On Friday, May 25, 2012 11:49:51 AM UTC-4, David McKeone wrote: >>>> >>>> Hi Massimo, >>>> >>>> "You probably do not need 100 models defined for each request." >>>> and "Make sure you turn migrations off and bytecode compile your apps." >>>> >>>> No, I certainly don't need all 100 at all times. That was really just >>>> a test to see where the boundaries were going to be. It likely wasn't the >>>> optimal configuration (migrations were off, wasn't byte-compiled), but it >>>> did highlight that as the app grows that's an area I have to watch for and >>>> one that will affect the user experience. Once I saw that a boundary >>>> existed I found Bruno's model-less design and that brought things back to >>>> great performance levels. So I think that design will fit my needs >>>> performance wise. >>>> >>>> I'll investigate the conditional model system, but my understanding of >>>> that was that you would be restricted to specific controllers. As in, I >>>> can't use a single table (model) across multiple controllers. Would that be >>>> true? >>>> >>>> -David >>>> >>> >> On Friday, May 25, 2012 8:05:06 PM UTC+1, Cliff Kachinske wrote: >>> >>> Maybe you could soft link the model files. >>> >>> For controller foo you would have a file models/foo/foo.py >>> >>> If controller bar needs needs data from table foo, you would create a >>> soft link in you models/bar directory to models/foo/foo.py. >>> >>> Note if you link it in as foo.py, it will run after bar.py, so you would >>> want to name the link according to the necessary sequence. >>> >>> Don't know what this would do for migrations on the production box, >>> though. >>> >>> On Friday, May 25, 2012 11:49:51 AM UTC-4, David McKeone wrote: >>>> >>>> Hi Massimo, >>>> >>>> "You probably do not need 100 models defined for each request." >>>> and "Make sure you turn migrations off and bytecode compile your apps." >>>> >>>> No, I certainly don't need all 100 at all times. That was really just >>>> a test to see where the boundaries were going to be. It likely wasn't the >>>> optimal configuration (migrations were off, wasn't byte-compiled), but it >>>> did highlight that as the app grows that's an area I have to watch for and >>>> one that will affect the user experience. Once I saw that a boundary >>>> existed I found Bruno's model-less design and that brought things back to >>>> great performance levels. So I think that design will fit my needs >>>> performance wise. >>>> >>>> I'll investigate the conditional model system, but my understanding of >>>> that was that you would be restricted to specific controllers. As in, I >>>> can't use a single table (model) across multiple controllers. Would that be >>>> true? >>>> >>>> -David >>>> >>>
