Time out issue?

I am trying to track down a time out issue I am having. It's weird though.

The long and short of it (I can add more details if you like), is that I was making something like a "super product template", which would have been a product listing that had all the options I might want for a class of products. Then, from the super product template, I would copy it and then subtract the product attributes I didn't need for the other product listings. The one thing of note that I didn't think to be an issue at the time since I am on local host was that the original files sizes of those images where around 500KB each.

Well, the weird part (to me) is this ... when I try to access the category that the super product template is in, the category page itself times out.

So I decided to move that product template over to a different category just to see what might happen. That different category then had the problem of timing out, whereas, the former category was just fine and did not time out.

After this, I decided to create a new product from scratch, and, instead of using Image squares as my control type for a Product attribute, I used Color squares. I did have about 5 Image squares in use, but I made sure that the original images were around 50KB each.

When I try to access this new product within a different category, again, the category page that shows the product listing still times out.

When I try to access older categories containing older product listings that are set up the same way, the category pages work as they should.

I tried a few things such as extending the time outs in nginx as well as changing the proxy from localhost to 127.0.0.1:5000, but I still get the time out.

In the error log, in nopCommerce, I don't have a reference to the errors.

In the error log, in nginx, I stopped getting errors around three hours ago when I made the different changes that I researched (which I can get you the links to if you like).

Still, even without the errors, I get either a timeout or a very long wait for those particular pages to resolve. For instance, I am still waiting on one to resolve, and I wrote this entire post while I have been waiting. ??

Below is the nginx error log marking from yesterday into today and into when I changed the store's URL ... (please note that mail.punkydoggear.com is something I happened to do when getting mail to work locally, I somehow changed my computer to become mail.punkydoggear.com - I don't know how, but it got the mail to work).

Also ... I had placed a note in my forums on local host to note one of the changes I had done. Then I went from that page back to the category in question to see if it resolved it, which it hadn't. That category page I had trouble resolving was pdg-store-2.

Another issue is that once I try to access one of these two category pages, my CPU starts climbing up into the high 90% usage range. The only thing that seems to stop it is to stop the nopcommerce service. My CPU was at 85% a few seconds ago. When I stopped the nopCommerce service, it quickly scaled back to 47.7%.

2023/03/21 23:22:59 [error] 926#926: *573 upstream timed out (110: Connection timed
out) while reading response header from upstream, client: 127.0.0.1, server:
mail.punkydoggear.com, request: "GET /Admin HTTP/1.1", upstream: "http://127.0.0.1:5000
Admin", host: "localhost", referrer: "http://localhost/"

2023/03/22 00:27:46 [error] 926#926: *2637 upstream timed out (110: Connection timed
out) while reading response header from upstream, client: 127.0.0.1, server:
mail.punkydoggear.com, request: "GET /pdg-store-2 HTTP/1.1", upstream: "http://[::1]:5000
pdg-store-2", host: "localhost", referrer: "http://localhost/boards/topic/18/automatically
refresh-page-on-502-bad-gateway-error"

2023/03/22 00:28:46 [error] 926#926: *2637 upstream timed out (110: Connection timed
out) while reading response header from upstream, client: 127.0.0.1, server:
mail.punkydoggear.com, request: "GET /pdg-store-2 HTTP/1.1", upstream: "http:/
127.0.0.1:5000/pdg-store-2", host: "localhost", referrer: "http://localhost/boards/topic/18
automatically-refresh-page-on-502-bad-gateway-error"

2023/03/22 01:04:49 [error] 926#926: *3772 upstream timed out (110: Connection timed
out) while reading response header from upstream, client: 127.0.0.1, server:
mail.punkydoggear.com, request: "GET /pdg-store-2 HTTP/1.1", upstream: "http://[::1]:5000
pdg-store-2", host: "localhost", referrer: "http://localhost/boards/topic/18/automatically
refresh-page-on-502-bad-gateway-error"

2023/03/22 01:05:49 [error] 926#926: *3772 upstream timed out (110: Connection timed
out) while reading response header from upstream, client: 127.0.0.1, server:
mail.punkydoggear.com, request: "GET /pdg-store-2 HTTP/1.1", upstream: "http:/
127.0.0.1:5000/pdg-store-2", host: "localhost", referrer: "http://localhost/boards/topic/18
automatically-refresh-page-on-502-bad-gateway-error"

Update: (This is a preliminary finding - not for sure yet)

I made a copy of a product within one of the slow-to-resolve categories and started deleting Product attributes from the product on a one by one basis.

After I deleted the first attribute where I had used parentheses in the title, I then tried to access the category in question. It was slow but faster than before to resolve.

I had three Product attributes where I had used parentheses, so I deleted each, one at a time, and tried to access the category in question each time. Each time, my access to the category became quicker.

When I had deleted all of the Product attributes where I had used parentheses, when I tried to access the category in question, it resolved just as quickly as the other categories I had tried.

Maybe the code doesn't like what I have as text in the title in between the parentheses for the Product attributes, which is the word (Color). I left the Product attribute Material Examples in place, and that didn't cause any issues with access time.

Product Attributes
Material Examples    Image Squares  0      
Webbing (Color)      Color Squares  1      
Canvas (Color)      Color Squares  2      
Mesh (Color)      Color Squares  3

No dice. The parentheses don't seem to be the answer. Still testing.

Each of the Product attributes have several values ... 22, 23, and 39, which total 84 values tied to three Product attributes within one Product listing. When I deleted the Product attribute with the most values (39), the access time to the category that contained the Product listing was quicker than before. When I deleted either of the other two Product attributes, the access time improved. Finally, when I deleted the last Product attribute, the access time was the quickest time.

That testing is as far as I have gotten in this mystery.

Are the amount of Product attribute values associated to a Product listing contingent on the processing speed of a category page rendering out that has that Product listing in it?

It's hard to understand if your 'performance' issue is separate from your 'timeout' issue.  If you do think the SQL is the root of your problems, then you may have to do SQL profiling.  (It's possible that just adding indexes could help.)

Well, when I put the same product listings on the home page, the same thing happens (the page chokes), but when I put links to the images in the HomepageText Topic ("Welcome to our store!"), the homepage renders just fine and is quick as designed. The links also in the Topic page, they also resolve quickly when accessed. I've decided to just go that way for the time-being. I don't think the software was designed to do what I am asking it to do.