Generated types for performance #404

Activity

1. charlesroddie commented on Jan 18, 2021

   

   charlesroddie

   on Jan 18, 2021

   Last edited by charlesroddie

   Author

   More actions

   A workaround which generates types usable from other projects in a standard way, is to create functions or types out of the provided types in a separate project.

   E.g. files containing:

   let myUserDefinedFunction(conn:SqlConnection) (arguments...) = async {
       use cmd = new db.MyUserDefinedFunction(conn)
       return! cmd.AsyncExecute(arguments...)
       }

   Split over a number of files to maintain IDE performance.

   Then a referencing project will become snappy to work with. This makes IDE performance manageable, at the cost of additional code. It doesn't improve runtime performance which is negligibly affected.
2. smoothdeveloper commented on Jan 19, 2021

   

   smoothdeveloper

   on Jan 19, 2021

   Collaborator

   More actions

   @charlesroddie thanks a lot for explaining how you work around IDE performance issue.

   The main issue for switching for generated types is that there needs to be a way to generate the IL, I'm not familiar but it would be significant work.

   In my use case, I have files with a bunch of SqlCommandProvider pointing for each .sql file, all in a single F# file, and similar as you say, helper functions broken down in domain specific files.

   There seems to be some incompressible amount of work when the IDE initialize a project that uses the provider and I think it is more related to the TP SDK and how it binds to the tooling rather than this specific provider.

   After the tooling initialized the project, the tooling performance is acceptable, I have a hundred or so of .sql files and didn't seem it wouldn't scale linearly.
3. github-actions

   added

   enhancement

   performance

   on Mar 7, 2026