Course enrollment admin is slow

[MaferMazu]

Description

"Course enrollment admin is slow" was a report from SD after migration.

Talking with @Ian2012, he thinks the problem is in the ordering. By default, the query order with user_id is 97secs, and without order, it takes 70secs.

We need to find where that class is ordered and modify it to solve this. If the product review accepts this, I don't know if we can extract this from the custom features in edx-platform to some eox or if we need to maintain this.

Extra info: https://user-images.githubusercontent.com/35668326/221997715-8ffabc76-bef7-46fb-8d93-4ce1cfd5dbc8.png

[santiagosuarezedunext]

@Ian2012 me podrias explicar un poco más sobre que es "Course enrollment admin" y el problema por favor 👍

[Ian2012]

Cuando se carga la tabla course enrollment en el panel de administración, este carga demasiado lento. Todo indica que es por el ordering que se aplica a esa tabla, en lilac los registros no se ordenaban, ahora si se ordenan y carga muy lento

[santiagosuarezedunext]

@MaferMazu ¿esto hace parte de las cosas custom que mantenemos o entendí mal? Si si hace parte ¿deberiamos registrarla en nuestra tabla de deprecaciones y darle proceso por ahí?

[MaferMazu]

Es un feature request. Es algo que está solicitando service delivery, es algo nuevo.

[santiagosuarezedunext]

@MaferMazu what do you mean with this: " I don't know if we can extract this from the custom features in edx-platform to some eox or if we need to maintain this."

[MaferMazu]

It means I don't know if we can implement a solution for this somewhere different from edunext-platform. If we can't that means adding a new custom feature to maintain in the list we try to empty.
Maybe a good idea is to avoid adding this to maintain and try to push the solution upstream. We can try to find out why the edx-platform is ordering, and propose not to order (but we need strong arguments).

[santiagosuarezedunext]

Okay, I think if we make the change we should make it upstream.

@Ian2012
Since this doesn't drastically affect anyone, upstreaming it can be delayed and right now we are working on upstreaming other features, i'm going to move this to the backlog and we'll take it when we have time.