Edit this page | Blame

Improve Menu Generation and Move it to GN3

Tags

  • assigned: fredm
  • type: bug
  • priority: medium
  • status: closed, completed
  • keywords: menu generation, GN2, GN3

Description

The

function calls functions that make queries to the database within loops.

This ruins the performance of the system significantly.

The queries should be reworked, and the code should be moved to GN3 since it does database access.

TODOs

  • [ ] Rework the queries: don't run queries inside loops
  • [x] Move the code to GN3
  • [x] Provide results of function at an endpoint in GN3

Update: 2022-05-26

Commits

enable the fetching of the menu items from GN3. They also report in case of any errors fetching the data from the server.

There is still a need to remove the code from GN2 but it might be a while since it is seemingly used in more than one place.

Update: 2022-06-23

Commits

move the menu generation code to GN3, and have GN2 only handle the display.

I have also made changes to some of the functions to optimise the queries to the database.

The remaining functions have proved really difficult to detangle and optimise, so for now I will mark this issue as done, until such a time as the performance of the menu proves to be unnacceptably slow.


(made with skribilo)