This meeting involved discussions with the State Changers, focusing on the issues faced by Cameron when using Xano. There was a problem where Cameron's event log function was timing out, and the participants analyze the function scenario and the existing structure of source code.
A key issue was the large amount of queries being run due to the structure of the function, where iten was dealing with many player statistics data. The team proposed the idea of optimizing performance by reducing the number of write operations with the help of index lookup and strategic 'add or edit records' executions. They recommended adding a unique index on the unique ID to increase query speed on the Xano platform, followed by incorporating a get record function to verify existing data before performing an add or edit operation. They further suggested implementing a conditional statement to restrict the number of add or edit operations, thus effectively controlling the task progression and handling timeout issues. The counter was introduced to implement a form of 'exit early' strategy when a certain number of database write operations were performed. These suggestions aimed to optimize operations, reduce timeouts, and provide Cameron with more control over the function's execution. However, this approach needs to be tested to verify its effectiveness. Note: The following keywords were not explicitly mentioned: "WeWeb", "FlutterFlow", "Zapier", "Make", "Integromat", "Outseta", "Retool", "Bubble", "Adalo", "AppGyver", "AppSheet", "Comnoco", "Fastgen", "Firebase", "Google", "OAuth", "Stripe", "Twilio", "Airtable", "DraftBit", "Javascript", "Typescript", "React", "Vue.js", "JSX", "HTML", "CSS", "lambda", "serverless", "State Change", "ScriptTag", "OpenAI", "AI21".
(Source: Office Hours 11/23 )
