[native]Advance velox version and update memory usage

prestodb · Jun 5, 2024 · 36f7d62 · 36f7d62
1 parent 7443f83
commit 36f7d62
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/presto-native-execution/presto_cpp/main/PrestoTask.cpp b/presto-native-execution/presto_cpp/main/PrestoTask.cpp
@@ -370,7 +370,7 @@ protocol::TaskStatus PrestoTask::updateStatusLocked() {
   }
 
   const auto veloxTaskMemStats = task->pool()->stats();
-  info.taskStatus.memoryReservationInBytes = task->pool()->usedBytes();
+  info.taskStatus.memoryReservationInBytes = veloxTaskMemStats.usedBytes;
   info.taskStatus.systemMemoryReservationInBytes = 0;
   // NOTE: a presto worker may run multiple tasks from the same query.
   // 'peakNodeTotalMemoryReservationInBytes' represents peak memory usage across
@@ -547,7 +547,7 @@ void PrestoTask::updateMemoryInfoLocked(
   protocol::TaskStats& prestoTaskStats = info.stats;
 
   const auto veloxTaskMemStats = task->pool()->stats();
-  const auto currentBytes = task->pool()->usedBytes();
+  const auto currentBytes = veloxTaskMemStats.usedBytes;
   prestoTaskStats.userMemoryReservationInBytes = currentBytes;
   prestoTaskStats.systemMemoryReservationInBytes = 0;
   prestoTaskStats.peakUserMemoryInBytes = veloxTaskMemStats.peakBytes;

diff --git a/presto-native-execution/velox b/presto-native-execution/velox