796987 - Change back search results pages to 10 per page

Status: RESOLVED FIXED

Description

[Ricky Rosario [:rrosario, :r1cky]]

When we were doing bucketed search, we moved changed our search pagination from 10 to 20 because we wanted to show 10 articles at the top. Now that we have unified search, we should switch back to 10 results. This will make the page load faster and will give less options to the user which will hopefully be a positive net result

Comment 1

[Will Kahn-Greene [:willkg] ET needinfo? me]

I definitely agree we should do this at some point in the future, but we shouldn't do it until we feel confident that the top 10 results are solid for some definition/measure of "solid".

Comment 2

[Ricky Rosario [:rrosario, :r1cky]]

Assigning to a sprint so we can discuss it then.

Comment 3

[Kadir Topal [:atopal]]

Just to be clear, the goal here is to reduce the page load time, right?

Comment 4

[Ricky Rosario [:rrosario, :r1cky]]

Performance will improve. Also, less is more?

Comment 5

[Kadir Topal [:atopal]]

I think we should go ahead and do this, but also test both assumptions.

Comment 6

[Ricky Rosario [:rrosario, :r1cky]]

(In reply to Kadir Topal [:atopal] from comment #5)
> I think we should go ahead and do this, but also test both assumptions.

I think this should be one of the last things we do. We need to be confident enough in our first 10 results to the point where we feel that showing more doesn't help.

Comment 7

[Ricky Rosario [:rrosario, :r1cky]]

I think we may need to hold off on this unless Kadir has a chance to do the CTR analysis before the Holidays?

Comment 8

[Kadir Topal [:atopal]]

This depends on the CTR data being backfilled for https requests. Either way, we should probably leave this for after the holidays.

Comment 9

[Ricky Rosario [:rrosario, :r1cky]]

(In reply to Kadir Topal [:atopal] from comment #8)
> This depends on the CTR data being backfilled for https requests. Either
> way, we should probably leave this for after the holidays.

Sounds good to me. Moving to next sprint.

Comment 10

[Cor vL (cor-el)]

Can we possibly have this number of results configurable (e.g. via a GET parameter: &results=20) if this change is being made?

Sometimes I do a search for posts by a specific user if I suspect that some replies need editing or otherwise action needs to be taken.
Also, I like to see as much results as possible when searching (I always set Google results to 100) if a question has been posted before and seeing more results makes it easier to pick out the ones that look promising before continuing to a next page of results.
Having to load more result pages and opening results that appear to be not helpful after all  to me takes more time with less results per page.

cor-el

Comment 11

[Will Kahn-Greene [:willkg] ET needinfo? me]

(In reply to Cor vL from comment #10)
> Can we possibly have this number of results configurable (e.g. via a GET
> parameter: &results=20) if this change is being made?
> 
> Sometimes I do a search for posts by a specific user if I suspect that some
> replies need editing or otherwise action needs to be taken.
> Also, I like to see as much results as possible when searching (I always set
> Google results to 100) if a question has been posted before and seeing more
> results makes it easier to pick out the ones that look promising before
> continuing to a next page of results.
> Having to load more result pages and opening results that appear to be not
> helpful after all  to me takes more time with less results per page.
> 
> cor-el

You should write up a new bug for that enhancement request.

Comment 12

[Kadir Topal [:atopal]]

moving to next sprint as the results will only come in during the 2013.1 sprint.

Comment 13

[Will Kahn-Greene [:willkg] ET needinfo? me]

I just skimmed the comments and it seems like this bug is waiting on CTR analysis from Kadir before it's ok'd to move ahead.

Has that been done? Is it ok to do this, yet?

Comment 14

[Kadir Topal [:atopal]]

Yes, it was done and the results presented at the last monday meeting. We can go ahead and test this. I'll make sure to monitor the CTR and file a follow up bug if we see a decrease in the CTR.

Comment 15

[Will Kahn-Greene [:willkg] ET needinfo? me]

https://github.com/mozilla/kitsune/pull/1074

Comment 16

[Will Kahn-Greene [:willkg] ET needinfo? me]

Oops--retroactively grabbing this one.

Comment 17

[Will Kahn-Greene [:willkg] ET needinfo? me]

Landed in master in https://github.com/mozilla/kitsune/commit/0e398c8d2784a895fb398afcb5bc58ec3f6af990

Comment 18

[Will Kahn-Greene [:willkg] ET needinfo? me]

Someone pushed this to production at some point in the last 12 hours or so.

Anyhow, I verified that production is now showing 10 results per page. Marking this one as FIXED.