Skip to content

Pre-building common libraries in the container #24

@milancurcic

Description

@milancurcic
Member

When first building stdlib, it takes a while for the playground to respond because it takes a while to build stdlib. Building and running programs that use stdlib subsequently is faster because the stdlib is reused, at least for this running session of the backend server.

I wonder if it would be a good idea and easy to implement to pre-build any built-in libraries (for now just stdlib) at docker build stage, rather than at server run time?

Activity

ashirrwad

ashirrwad commented on Sep 6, 2022

@ashirrwad
Member

That's what I used in the first iteration but as @everythingfunctional stated it would mean that all the libraries are built which won't be useful if the user only imports some selected libraries.

everythingfunctional

everythingfunctional commented on Sep 6, 2022

@everythingfunctional
Member

If I recall, the initial implementation wasn't pre-building them, but maybe I'm mistaken. This might be worth considering.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @everythingfunctional@milancurcic@ashirrwad

        Issue actions

          Pre-building common libraries in the container · Issue #24 · fortran-lang/playground