Flux
#17
Replies: 1 comment
-
|
I'd like to see more of what you have going on, to see if it's a circular component reference (which isn't currently supported), or if something else is going on. What is your memory limit set to? Feel free to email me at [email protected] with extra details that might help out (if you are able), referencing this discussion in the email. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
First of all thank you for the effort in this package. For applications with thousands of views on a page you are helping to greatly increase performance.
Is it possible to use this with Livewire Flux?
I am converting Flux blade components to Dagger components in order to lower views rendered and increase performance. It somewhat works but has issues.
On the first couple loads of the page memory usage is around 120MB and takes about 1sec to load. The page has about 40 total Dagger components. On subsequent renders we're down to 3MB in memory and 65ms.
The issue is when I add any further Dagger components- which are flux blade components converted - I get a memory exhaustion error. Have the PHP settings at 512MB.
I'm unsure if I'm doing something incorrectly and I'd like to share the components but unsure if I'm able to share them due to Flux licensing.
Happy to share more details privately or publicly if licensing allows in order to give more information if needed.
Beta Was this translation helpful? Give feedback.
All reactions