k

In Firefox, the search is not only slow, but also locks up my browser until it's done loading the updated icon set. The delay is about 10-20 seconds before it will respond to input again.

I do a lot of searches, so I often use a different browser for TF2OP Steam Inventory searches, and copy the search results URL back into my main browser. So I can do something else while I wait for it.

I'd be happy with some kind of advanced search mode without the nice icons, if that could be faster.

Slowing down the auto-updating of the icons as the user types would also be an improvement, because at the moment, if I type too slow or mistype, it pauses for 15+ seconds to update the list again. I got into the habit of copy pasting the search text, to avoid this, but it doesn't strip leading/trailing spaces on the clientside, so it's easy to screw this up as well.

The search still works fairly well for the other apps, but the list of Steam items is now so long that it's making the search hard to use.

when i try to do it. it says its not public but it loads all other backpacks?
Admin plz read this

Originally posted by I.G.O.S v1.9.9:

when i try to do it. it says its not public but it loads all other backpacks?
Admin plz read this

Set your Steam Gift inventory to public as well not just your inventory.

As for the current search system, it's been discussed it's terribly inefficient. I hope something is being done about it.

It is because there are so many people already trying to load their backpack, it causes stress on the servers.
And I think the recent steam badge thing got a lot more users active, both on tf2op's end and steam's end.

One of the reasons for that is that it uses the Steamcommunity API and those servers are much slower/more loaded.

Originally posted by Zemnmez's birthday is today:

One of the reasons for that is that it uses the Steamcommunity API and those servers are much slower/more loaded.

Doesn't backpack.tf use the Steamcommunity API? Haven't experienced such problems there.

Originally posted by norby89:

Originally posted by Zemnmez's birthday is today:

One of the reasons for that is that it uses the Steamcommunity API and those servers are much slower/more loaded.

Doesn't backpack.tf use the Steamcommunity API? Haven't experienced such problems there.

For Steam Inventory and similar, the APIs are on steamhost.cn/steamcommunity_com; for TF2 and other games and steam OpenID auth, the steampowered servers are used, which are much faster.

Originally posted by Zemnmez's birthday is today:

For Steam Inventory and similar, the APIs are on steamhost.cn/steamcommunity_com; for TF2 and other games and steam OpenID auth, the steampowered servers are used, which are much faster.

So is it possible to cache the list of games, items, icons, etc.? Updates aren't real-time as it is.

Originally posted by SheeEttin:

So is it possible to cache the list of games, items, icons, etc.? Updates aren't real-time as it is.

Yes, it should be, and I don't know if they are.

The Servers are overloaded as simple as that.

Originally posted by THE_ART_OF_KILLING:

The Servers are overloaded as simple as that.

Yeah, 3700 users at once I read before, it's mindblowing. If you imagine it as a house, the house is how large?

There are 2 separate issues being discussed here

The backpack view could be slowed down by delays waiting for the Steam APIs to return the data, but this problem should not have any effect on searching for trades. When you set up a search, you're seeing a list of every item that exists for the app that you have selected (like TF2 or Steam), so there's no need to load anyone's inventory.

(There is an API call to get the encoded URLs for thumbnails, etc, but I assume these are cached, or TF2OP would use up its API call quota too fast)

My impression is that the delays in the search interface are a combination of the search interface script running inside your browser being quite resource-intensive, and the need to fetch a really huge set of thumbnails from the steam content server (or check that they're unchanged, anyway). The delays are all in the interface, the search itself is usually really quick. There doesn't seem to be a problem with TF2OP's server.

Maybe if the search interface was faster, we would then start to see problems with the search itself getting slower to return results, because people could search more frequently and stress TF2OP's server more ;)

Originally posted by THE_ART_OF_KILLING:

The Servers are overloaded as simple as that.

Wrong. Loading Steam items on outpost was always a pain in the ass, even when I try to open my own inventory, the site still loads all the items

Originally posted by Potato:

There are 2 separate issues being discussed here

The backpack view could be slowed down by delays waiting for the Steam APIs to return the data, but this problem should not have any effect on searching for trades. When you set up a search, you're seeing a list of every item that exists for the app that you have selected (like TF2 or Steam), so there's no need to load anyone's inventory.

(There is an API call to get the encoded URLs for thumbnails, etc, but I assume these are cached, or TF2OP would use up its API call quota too fast)

My impression is that the delays in the search interface are a combination of the search interface script running inside your browser being quite resource-intensive, and the need to fetch a really huge set of thumbnails from the steam content server (or check that they're unchanged, anyway). The delays are all in the interface, the search itself is usually really quick. There doesn't seem to be a problem with TF2OP's server.

Maybe if the search interface was faster, we would then start to see problems with the search itself getting slower to return results, because people could search more frequently and stress TF2OP's server more ;)

Many people complain about the icons taking a while to load, but it's not a huge issue, because the images load asynchronously- you can start searching as soon as "loading something interesting" has closed, while the images are still loading.