Hi,
I got below error while clicking on the run on sandbox.

atal error: Allowed memory size of 104857600 bytes exhausted (tried to allocate 262131 bytes) in /home/cook/sites/www.j-cook.net/public_html/administrator/components/com_jcook/fork/helpers/layouter.php on line 481
Error : Allowed memory size of 104857600 bytes exhausted (tried to allocate 262131 bytes)

Regards
Vivek

This is the limit.
Split your project in parts.

Sorry about that..I didn't know that jcook has a limitation on the number of tables in a project.I deleted the last table I had added and it worked fine.


Regards
Vivek

Hello Admin

Thanks for your feedback.

Many of my projects are empty. Most or all of the tables are gone. Why?

MUL, EMR and others still have the following errors:I have searched the forum and found that this issue was fixed for many other users but it still persists in my case.

I have found that even my smallest projects were about 15 - 20 tables. You speak of splitting large projects:
1. Can you outline the details for splitting projects in J-Cook or point to a doc which can help?
2. What are the indicators that should tell a developer that it is time to split a project?
3. What are the upper limits in terms of tables or bytes for a project?
4. How do I split a project if the tables are not visible?

Please help, my productivity in the j-cook builder has fallen to zero because of issues such as these. I am also unable to download these projects.

Thanks again
v

Ok, I can upsize a little bit more, but then I reach the physical limits.
There are no indicator of the memory you are using, but I can do it to help you better.

I upsized to 120Mo and I will not do more.
You must also reduce your component.

Hello Admin

Thanks for the help. I am still faced with the same issue while trying to download my component. I don't know what can be done at this point but any additional assistance would be greatly appreciated.

Regards
V

New error:

I have deleted almost a third of the tables in one of my oldest JCook projects (funeral one), deleted views, removed FK's and I am still getting errors. On the old builder I never had any issues, but now I want to try J3 and the new forking system.. however I am constantly getting

Allowed memory size of 125829120 bytes exhausted (tried to allocate 35 bytes)

No matter how much I delete, that 35 bytes never seems to change other than to go a little higher or a little lower.. but it always 2 figures

I now cant delete any more, and I understand how you, correctly, cant allocate any more memory.

Can you give me a clue on how much I need to delete or change to make this work? Any chance of a future 'counter' or % bar so we know what to aim for?

Thanks

Now you can download your dataset alone if you want.

Try to reduce your huge table, I think it can be the problem in your case.
Cut it in 3 tables linked in 1:1 (some code to write)

option : Delete some layouts, and create them manually (it is always the same, and easy)
option : Delete some fields, create manually

option : Split your project in 2 or 3 parts. (components) ... And then try to merge them.
Or work with a main component and satellites components... with loader.php is is really easy

When you cut your component, try to cut less FK possible, because you will need to recreate.

If you are patient, in close future I want to add the pssibility to catch Third tables (make connections between your projects, or other...)

support for "Third tables" would be great ... I've been splitting my component as suggested for quite some time and this would be a huge help!

Dave

Splitting components would be fine if I had expected it and planned from the start I suppose.. sigh..

Feature suggestion - duplicate a project so I can cut them both in half.. with half each as opposed to having to recreate 50% of the work.. =)

sigh again! when have the heart, I will do the job, for now its just too disheartening. I have already destroyed 1/3rd of my work and still cant download my component. I am just working on the last download I did from the old builder for now.. I will take advantage of the new builder at a future date. Gonna try removing a little more code with my fingers crossed!

heh heh, who said having a moan doesnt work.. took out a few more links and I can now download the component... loads to do to recreate what was lost, but at least I have a starting point

If my understanding of the issue is correct, cook basically needs to load the entire project into memory all at once. Therefore, large projects timeout based on a number of issues including network latency, memory size, etc.

Assuming that this is the case; can cook not store most of a user's component-data in an encrypted file on the local hard drive such that requested components are loaded from there? Of course, this will introduce file synchronization and other challenges, but it would allow j-cook to overcome latency issues, which to my mind is a fatal flaw in what is otherwise a great builder.

As suggested before, another function which would complement this environment and make splitting projects more desirable, is the ability to copy a project. I have a project with 74 tables; created when I first joined the community and long before I knew about any j-cook limits on project size. To ask me to split this into 7, 10 table projects in the current builder is really to ask me to build 6 new projects from scratch. That is not easy or feasible after I have spent so much time working on that one. Based on the project request I undertake, I am unable to do anything useful in a 10 table project.

Local data-files and project cloning as a matter of urgency in J-cook, just suggestions and personal wish list...
V

I undersdand.

Well, Cook has grown up a lot but you still cannot see it because it does quite the same than before. The ressources used are 2 or 3 times more consequent. This is normal. So at the beginning, Cook was handling a project with 74 (like you say). But now, it is more difficult.
I am gonna resize my VPS or change for a cloud, and increase the memory limits in future. Currently, I am in limit.

My next idea is to give you the Mo used at the last build, so you will be able to know the limit.
Actually the limit is 120Mo. Because, yes the whole project is loaded in memory at once when it is generating. The generation process is creating a lot a objects and dependencies and parsers and .... for every single objet (table, field, filter, ...)

About cloning and third tables, I would like to do it soon, but deal with priorities.
Latest version : 2.5.5
www.j-cook.net/index.php/docs/versions/82-2-5-5