Giter Club home page Giter Club logo

Comments (3)

fangweili avatar fangweili commented on May 23, 2024

No, we don't export graph and weights separately. For a graph with multiple "datasets", it should be exported as multiple "versions" of the same model. We want model exports to be self-contained. Besides, in most cases, the footprint of graph itself is relatively small/insignificant compared to its weights in serialized format.

Yes, multiple versions of a model can be loaded simultaneously and used by the same Classify() interface. We don't currently have an example for that. But you can implement it easily through either StaticManager (if you have a static list of versions to load) or custom FileSystemStoragePathSource (if you need capability of discovering new versions at runtime).

Could you tell us a bit more about the use case?

from serving.

viksit avatar viksit commented on May 23, 2024

Ah, thanks @fangweili - the multiple versions of the model makes sense.

Basically, I have discrete datasets for predicting labels (via the same model) that are under a taxonomy, with sublabels.

eg,

model_id_1 predicts label1.sublabel1, label1.sublabel2
model_id_2 predicts label2.sublabel1, label2.sublabel2

The models may (or may not share) the same graph. I'm building this system to be flexible in case I need different graphs per use case, or re-use the same one across all of them.

I've created a new StorageSourcePath based system that can discover models within a file system, and my own version of the AspiredVersionManager that can load different models into memory. With this, I can,

  • Either have /data/modelid/0001..0004 where modelid can have one graph and versions have different weights (trained for different datasets)
  • Or, I can have /data/modelid/001, /data/modelid2/001 where the model IDs encode different graphs.

from serving.

fangweili avatar fangweili commented on May 23, 2024

For "manager to load different models into memory", the recommended solution is to extend FileSystemStoragePathSource so that it "aspire" multiple versions instead of just the latest one. AspiredVersionManager will then keep the whole "aspired set" in memory - you don't have to change it.

from serving.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.