GaoSong
GaoSong
I beg your twice thinking about keeping such features by framework, they are very important in prediction-based work. If you decided to remove these features, I wonder whether there would...
> State and utilization history should not be stored be the framework. This has to be a user's decision. This way, such features should be removed In fact, vm.getUtilizationHistory() has...
@filiphr hi~, could you have a look at this pr when you have time please~~
> I will try @Qomolang. I'll try to bring this in with the 1.6 release. The only thing that I am afraid with this is the fact that it will...