New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[QUESTION] Allowed memory size. Bug or not? #2585
Comments
Your PHP process runs out of memory when reading your view file. I think 500000 rows is a bit too much for the FromView strategy. You can try the approach this article took: https://stefanzweifel.io/posts/lazy-collections-in-laravel-excel/ |
I cant use cursor() because use Laravel version: 5.5.*. And I get the data not only from database, through calculations in php, because the database does not allow such calculations. In any case, I will have an array with 500,000 rows, before I give it to the generator Excel file. |
@patrickbrouwers I tried the approach from the article but I get:
|
@fedeisas which version of laravel are you using? |
|
I'm using queued writes. Maybe that's the issue? I'm trying to do exports on distributed workers (using S3) and the So I'm trying to switch to lazy collections and |
@fedeisas use queue failed with error |
i still can't export 60K data with FromQuery concern or LazyCollection with 512M memory setting any other setting to implement this? |
This bug report has been automatically closed because it has not had recent activity. If this is still an active bug, please comment to reopen. Thank you for your contributions. |
Prerequisites
Versions
Description
got error
Additional Information
memory_limit = 1536M - I can’t set more
my code
Excel::download(new ReportExport($data), 'excel.xlsx');
$data
it collection data with 500000 rows +How can i write so much data ?
The text was updated successfully, but these errors were encountered: