Super Shop Wizard - Revision history

Huntertur: /* Notes */ Mention the Super Wiz

2024-08-03T19:36:18Z

Notes: Mention the Super Wiz

← Older revision		Revision as of 19:36, 3 August 2024
Line 723:		Line 723:
	* If the Super Shop Wizard is used from pages adhering to the 2021 redesign, <code>caller=h5</code> is set after <code>q</code> in the query string. <code>caller</code> is not present when using pages adhering to the 2007 redesign.		* If the Super Shop Wizard is used from pages adhering to the 2021 redesign, <code>caller=h5</code> is set after <code>q</code> in the query string. <code>caller</code> is not present when using pages adhering to the 2007 redesign.
	* If <code>priceOnly=1</code>, everything is still stuffed into <code>data</code>, and the query still takes seconds to run! There appears to be no performance benefit to checking this box. The only difference is in <code>html</code>; here's an example: <syntaxhighlight lang="html"><div class="ssw-result-priceonly">The 126 lowest prices of a One Dubloon Coin average out to:   2,719 NP</div></syntaxhighlight>		* If <code>priceOnly=1</code>, everything is still stuffed into <code>data</code>, and the query still takes seconds to run! There appears to be no performance benefit to checking this box. The only difference is in <code>html</code>; here's an example: <syntaxhighlight lang="html"><div class="ssw-result-priceonly">The 126 lowest prices of a One Dubloon Coin average out to:   2,719 NP</div></syntaxhighlight>
			* The Super Shop Wizard is sometimes inconsistently called the Super Wiz.

	== References ==		== References ==

Huntertur: Add example of failure

2024-08-03T16:11:38Z

Add example of failure

@@ Line 679: / Line 679: @@
 </syntaxhighlight>
 </div>
 == Notes ==
 * The response contains a lot of duplicate information. Compare <code>prices</code> with <code>price_str</code>, and the fact that the sample response contains 127 shops while the server-generated HTML that the UI actually uses is limited to the top 10. This suggests that only <code>req</code> and <code>html</code> are used, with the other values merely being intermediate variables that the server should not be sending to the client.
 * Everything except some elements of <code>req</code> is a string. However, the prices are presorted correctly despite all being strings.
 * If the Super Shop Wizard is used from pages adhering to the 2021 redesign, <code>caller=h5</code> is set after <code>q</code> in the query string. <code>caller</code> is not present when using pages adhering to the 2007 redesign.

Huntertur: /* Notes */ Note lack of performance benefit

2024-08-02T20:22:46Z

Notes: Note lack of performance benefit

← Older revision		Revision as of 20:22, 2 August 2024
Line 685:		Line 685:
	* Everything except some elements of <code>req</code> is a string. However, the prices are presorted correctly despite all being strings.		* Everything except some elements of <code>req</code> is a string. However, the prices are presorted correctly despite all being strings.
	* If the Super Shop Wizard is used from pages adhering to the 2021 redesign, <code>caller=h5</code> is set after <code>q</code> in the query string. <code>caller</code> is not present when using pages adhering to the 2007 redesign.		* If the Super Shop Wizard is used from pages adhering to the 2021 redesign, <code>caller=h5</code> is set after <code>q</code> in the query string. <code>caller</code> is not present when using pages adhering to the 2007 redesign.
	* If <code>priceOnly=1</code>, everything is still stuffed into <code>data</code>, and the query still takes seconds to run! There appears to be no benefit to checking this box. The only difference is in <code>html</code>; here's an example: <syntaxhighlight lang="html"><div class="ssw-result-priceonly">The 126 lowest prices of a One Dubloon Coin average out to:   2,719 NP</div></syntaxhighlight>		* If <code>priceOnly=1</code>, everything is still stuffed into <code>data</code>, and the query still takes seconds to run! There appears to be no performance benefit to checking this box. The only difference is in <code>html</code>; here's an example: <syntaxhighlight lang="html"><div class="ssw-result-priceonly">The 126 lowest prices of a One Dubloon Coin average out to:   2,719 NP</div></syntaxhighlight>

	== References ==		== References ==

Huntertur: /* Notes */ Add priceOnly

2024-08-02T20:20:40Z

Notes: Add priceOnly

← Older revision		Revision as of 20:20, 2 August 2024
Line 685:		Line 685:
	* Everything except some elements of <code>req</code> is a string. However, the prices are presorted correctly despite all being strings.		* Everything except some elements of <code>req</code> is a string. However, the prices are presorted correctly despite all being strings.
	* If the Super Shop Wizard is used from pages adhering to the 2021 redesign, <code>caller=h5</code> is set after <code>q</code> in the query string. <code>caller</code> is not present when using pages adhering to the 2007 redesign.		* If the Super Shop Wizard is used from pages adhering to the 2021 redesign, <code>caller=h5</code> is set after <code>q</code> in the query string. <code>caller</code> is not present when using pages adhering to the 2007 redesign.
			* If <code>priceOnly=1</code>, everything is still stuffed into <code>data</code>, and the query still takes seconds to run! There appears to be no benefit to checking this box. The only difference is in <code>html</code>; here's an example: <syntaxhighlight lang="html"><div class="ssw-result-priceonly">The 126 lowest prices of a One Dubloon Coin average out to:   2,719 NP</div></syntaxhighlight>

	== References ==		== References ==

Huntertur: /* Notes */ Note caller parameter

2024-08-02T20:17:12Z

Notes: Note caller parameter

← Older revision		Revision as of 20:17, 2 August 2024
Line 684:		Line 684:
	* The response contains a lot of duplicate information. Compare <code>prices</code> with <code>price_str</code>, and the fact that the sample response contains 127 shops while the server-generated HTML that the UI actually uses is limited to the top 10. This suggests that only <code>req</code> and <code>html</code> are used, with the other values merely being intermediate variables that the server should not be sending to the client.		* The response contains a lot of duplicate information. Compare <code>prices</code> with <code>price_str</code>, and the fact that the sample response contains 127 shops while the server-generated HTML that the UI actually uses is limited to the top 10. This suggests that only <code>req</code> and <code>html</code> are used, with the other values merely being intermediate variables that the server should not be sending to the client.
	* Everything except some elements of <code>req</code> is a string. However, the prices are presorted correctly despite all being strings.		* Everything except some elements of <code>req</code> is a string. However, the prices are presorted correctly despite all being strings.
			* If the Super Shop Wizard is used from pages adhering to the 2021 redesign, <code>caller=h5</code> is set after <code>q</code> in the query string. <code>caller</code> is not present when using pages adhering to the 2007 redesign.

	== References ==		== References ==

Huntertur: /* Notes */ Add string stuff

2024-08-02T20:15:26Z

Notes: Add string stuff

← Older revision		Revision as of 20:15, 2 August 2024
Line 683:		Line 683:

	* The response contains a lot of duplicate information. Compare <code>prices</code> with <code>price_str</code>, and the fact that the sample response contains 127 shops while the server-generated HTML that the UI actually uses is limited to the top 10. This suggests that only <code>req</code> and <code>html</code> are used, with the other values merely being intermediate variables that the server should not be sending to the client.		* The response contains a lot of duplicate information. Compare <code>prices</code> with <code>price_str</code>, and the fact that the sample response contains 127 shops while the server-generated HTML that the UI actually uses is limited to the top 10. This suggests that only <code>req</code> and <code>html</code> are used, with the other values merely being intermediate variables that the server should not be sending to the client.
			* Everything except some elements of <code>req</code> is a string. However, the prices are presorted correctly despite all being strings.

	== References ==		== References ==

Huntertur: Increase range of runtimes

2024-08-02T20:14:00Z

Increase range of runtimes

← Older revision		Revision as of 20:14, 2 August 2024
Line 3:		Line 3:
	== /shops/ssw/ssw_query.php ==		== /shops/ssw/ssw_query.php ==

	The example ~~took~~ 1.35 seconds to run. Given how there is a ton of manual sharding going on based on the first letter of the username,<ref>https://www.jellyneo.net/?go=shopwiz</ref><ref>https://www.reddit.com/r/neopets/comments/1asklqr/nc_capsule_rerolls/ "There are many tables in neopets that are sharded (split) by username. Some, like this one, are split depending on the first character of the username. In this case, it means all users that start both with d and q will have their nc items in the same table, while users starting with c will be in another table."</ref> this is not surprising.		The example takes 1.35 to 3.50 seconds to run. Given how there is a ton of manual sharding going on based on the first letter of the username,<ref>https://www.jellyneo.net/?go=shopwiz</ref><ref>https://www.reddit.com/r/neopets/comments/1asklqr/nc_capsule_rerolls/ "There are many tables in neopets that are sharded (split) by username. Some, like this one, are split depending on the first character of the username. In this case, it means all users that start both with d and q will have their nc items in the same table, while users starting with c will be in another table."</ref> this is not surprising.

	=== Example request ===		=== Example request ===

Huntertur: Create page

2024-08-02T20:11:30Z

Create page

Show changes