EXTREMELY slow server

It sounds to be that your workers (processing the csv) take a lot of CPU usage and therefore the whole server is getting slower because the CPU usage is high. Normally when you process this amount of data it's wise to split this into multiple servers. The most ideal setup might even be to have a separate web server, database server and worker server. This means you have three servers, but if your workers are having a hard time you can either scale that server or add another server that is also reading from the queue.

Separating the database into a different server will also take down the CPU usage in the end. Right now you write and read a lot from the database and this takes time and memory. If you have this on a separate server you will probably get some extra speed as well.

Does this help you in any way? Do you have more questions? Let me know!

Thanks Bobby, I will split the program into different servers for my workers if needed. But even when no workers are running, and no files are being uploaded, its taking forever. I have one page for example:

$plan = Auth::user()->subscription()->stripe_plan;

        $uploads = Upload::where('user_id', Auth::user()->id)
            ->orderBy('created_at', 'DESC')
            ->where('created_at', '>=', Carbon::now()->subDays(14))
            ->paginate(25);

        $fileUploading = false;
        foreach($uploads as $upload){
            if($upload->uploading == true){
                $fileUploading = true;
            }
        }
        
        return view('uploads.index')
            ->with('plan', $plan)
            ->with('fileUploading', $fileUploading)
            ->with('uploads', $uploads);

This currently returns 30 uploads, one of which gets queried in blade ({{$uploads->leads()->count()} returning querying about 6k records. this page is taking over 30 seconds to load with no workers or uploads occurring right now.

Do you have proper indexing? Try dumping these queries into sql string and run on database to see how much time it needs to process. From my experience these sometimes are really slow. You use paginate which does query also for count, think of simple paginate instead if you don't need exact page count. Lastly, but not least you should make use of cache.

In this case the only indexed field would be user_id, which since is a foreign key gets indexed, correct? I have one user where the upload returns 1 record, even to load that it takes 20 seconds.

I will use simplepaginate instead and see if it helps any.

In my .blade.php file i have a lot of blade conditionals, could that drastically decrease performance?

Simple pagination helps A LOT if you have millions of records from my own experience. The count that is executed every time you fetch a page is killing the performance with the 'LengthAwarePaginator'. Millions of records in a table should not be a problem if your indexes are correctly set and you don't have any exotic queries.

I see you are sorting on 'created_at' do you have an index on that? In general you should have an index on each field you search and/or sort.

How does your website perform on your local machine?

Just something small, but your foreach can be 1 nanosecond 'quicker':

$fileUploading = false;
foreach($uploads as $upload){
      if($upload->uploading == true){
           $fileUploading = true;
           break; // no need to continue your foreach loop if you found one upload that is uploading 
     }
}

ill add an index on created at. Locally the site performs well, it was sort of a sudden thing where the website started slowing down. I looked at the processes running on the server, and it doesnt seem anything out of the ordinary. On digital forge, I can see the even CPU usage isnt maxed out and response time is still extremely slow.

ill add break statement.

Locally site works just fine.

Also try adding the laravel debugbar and see what, how much, and which queries are executed on different pages. It can help you figuring out where the problem is.

https://github.com/barryvdh/laravel-debugbar

currently i have two sites on the server, i tried moving the issue site off the current server and move to a completely separate one. i pulled the clockwork package and now whenever trying to pull to this same server i get the following:

Fetching origin
error: insufficient permission for adding an object to repository database .git/objects
fatal: failed to write object
fatal: unpack-objects failed
error: Could not fetch origin

is this referring to a permission issue from forge accessing github?

for others:

fixed my using password to access github . ^^

Locally is also quite slow. On Debug bar I see the queries that were ran (.75 seconds), but still took the page 20 seconds to load using 275mb of memeory

where do i see what is happing on the application side?

Booting (953.86ms) Application (18.63s)

The primary issue was an excessive number of blade conditionals and querys on the view. As of last week the file upload would work very well, now seems to have drastically slowed to. CPU usage is not maxed out so im not sure what caused it.

https://laracasts.com/discuss/channels/code-review/csv-upload