<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic What can I do to reduce the number of MLflow API calls I make? in Machine Learning</title>
    <link>https://community.databricks.com/t5/machine-learning/what-can-i-do-to-reduce-the-number-of-mlflow-api-calls-i-make/m-p/32041#M1687</link>
    <description>&lt;P&gt;I'm fitting multiple models in parallel.  For each one, I'm logging lots of params and metrics to MLflow.  I'm hitting rate limits, causing problems in my jobs.&lt;/P&gt;</description>
    <pubDate>Sun, 09 Jan 2022 01:10:38 GMT</pubDate>
    <dc:creator>Joseph_B</dc:creator>
    <dc:date>2022-01-09T01:10:38Z</dc:date>
    <item>
      <title>What can I do to reduce the number of MLflow API calls I make?</title>
      <link>https://community.databricks.com/t5/machine-learning/what-can-i-do-to-reduce-the-number-of-mlflow-api-calls-i-make/m-p/32041#M1687</link>
      <description>&lt;P&gt;I'm fitting multiple models in parallel.  For each one, I'm logging lots of params and metrics to MLflow.  I'm hitting rate limits, causing problems in my jobs.&lt;/P&gt;</description>
      <pubDate>Sun, 09 Jan 2022 01:10:38 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/what-can-i-do-to-reduce-the-number-of-mlflow-api-calls-i-make/m-p/32041#M1687</guid>
      <dc:creator>Joseph_B</dc:creator>
      <dc:date>2022-01-09T01:10:38Z</dc:date>
    </item>
    <item>
      <title>Re: What can I do to reduce the number of MLflow API calls I make?</title>
      <link>https://community.databricks.com/t5/machine-learning/what-can-i-do-to-reduce-the-number-of-mlflow-api-calls-i-make/m-p/32042#M1688</link>
      <description>&lt;P&gt;The first thing to try is to log in batches.  If you are logging each param and metric separately, you're making 1 API call per param and 1 per metric.  Instead, you should use the batch logging APIs; e.g. use "log_params" instead of "log_param" &lt;A href="https://mlflow.org/docs/latest/python_api/mlflow.html#mlflow.log_params" target="test_blank"&gt;https://mlflow.org/docs/latest/python_api/mlflow.html#mlflow.log_params&lt;/A&gt;&lt;/P&gt;&lt;P&gt;If you're logging 10 params and metrics per model, this will cut the number of API calls you're making by a factor of 10.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this optimization is still insufficient for you, then I'd recommend doing 2 things:&lt;/P&gt;&lt;P&gt;1) Short-term workaround: You can save data you wish to log to a table and log it in a follow-up process later.&lt;/P&gt;&lt;P&gt;2) Medium/long-term: I'd recommend working with your Databricks account team to come up with a solution to match your needs.  In general, the best option is to reorganize how models are being fit or logged to do more efficient batching in logging.  But different cases may have different best solutions, so working with your account team may be the best option.&lt;/P&gt;</description>
      <pubDate>Sun, 09 Jan 2022 01:15:50 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/what-can-i-do-to-reduce-the-number-of-mlflow-api-calls-i-make/m-p/32042#M1688</guid>
      <dc:creator>Joseph_B</dc:creator>
      <dc:date>2022-01-09T01:15:50Z</dc:date>
    </item>
  </channel>
</rss>

