-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ML] Improve the accuracy of model memory control #122
Changes from 1 commit
9f0ee3a
55e6dbe
e89c13c
f927102
af04280
fe5a063
b9413d9
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -652,7 +652,7 @@ std::size_t CTimeSeriesDecompositionDetail::CPeriodicityTest::extraMemoryOnIniti | |
if (result == 0) { | ||
for (auto i : {E_Short, E_Long}) { | ||
TExpandingWindowPtr window(this->newWindow(i, false)); | ||
result += core::CMemory::dynamicSize(window); | ||
result += 0.3 * core::CMemory::dynamicSize(window); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Don't we only compress on persist? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. In fact, no. As of #100, we compress the raw bytes of some this object we actually hold in memory. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ah, I recall you saying we'd do that but I missed the fact it's already in. Cool. |
||
} | ||
} | ||
return result; | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -95,7 +95,7 @@ CAnomalyDetectorModel::CAnomalyDetectorModel(bool isForPersistence, | |
: // The copy of m_DataGatherer is a shallow copy. This would be unacceptable | ||
// if we were going to persist the data gatherer from within this class. | ||
// We don't, so that's OK, but the next issue is that another thread will be | ||
// modifying the data gatherer m_DataGatherer points to whilst this object | ||
// modifying the data gatherer m_DataGatherer points too whilst this object | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This seems like a typo There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This was a typo before, the to[o] in this context means as well which is too rather than to. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It's still kind of a weird sentence but fair enough! There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Wait a sec, I'm sorry you're actually completely right. I'd somehow (repeatedly) misread! |
||
// is being persisted. Therefore, persistence must only call methods on the | ||
// data gatherer that are invariant. | ||
m_Params(other.m_Params), m_DataGatherer(other.m_DataGatherer), | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a cool language feature!