使用 PLINQ 时如何避免内存不足异常?

发布于 2024-12-25 12:13:21 字数 2433 浏览 1 评论 0原文

您好,感谢您的浏览!

背景

我有一个需要大量时间或并行计算的计算任务。

具体来说,我需要循环遍历大约 50 个图像的列表,对它们进行 Base64 编码,然后计算每个新编码的项目与包含大约 2000 个 Base64 字符串编码图像的 XML 文件中的值之间的 Levenshtein 距离,以便在具有最小 Lev 的 XML 文件。距基准弦的距离。

常规的 foreach 循环可以工作,但速度太慢,因此我选择使用 PLINQ 来利用我的 Core i7 多核处理器:

Parallel.ForEach(candidates, item => findImage(total,currentWinner,benchmark,item));

任务开始得很顺利,高速运行,但随后我出现“内存不足”异常。

我正在使用 C#、.NET 4、表单应用程序。

问题

如何调整 PLINQ 代码以免耗尽可用内存?

更新/示例代码

以下是调用以启动 PLINQ foreach 的方法

private void btnGo_Click(object sender, EventArgs e)
{
    XDocument doc = XDocument.Load(@"C:\Foo.xml");
    var imagesNode = doc.Element("images").Elements("image"); //Each "image" node contains a Base64 encoded string.
    string benchmark = tbData.Text; //A Base64 encoded string.
    IEnumerable<XElement> candidates = imagesNode;

    currentWinner = 1000000; //Set the "Current" low score to a million and bubble lower scores into it's place iteratively.
    
    Parallel.ForEach(candidates, i => {
        dist = Levenshtein(benchmark, i.Element("score").Value);
        if (dist < currentWinner)
        {
            currentWinner = dist;
            path = i.Element("path").Value;
        }
    });
}

: 。 .这是编辑距离法:

public static int Levenshtein(string s, string t)    {
            int n = s.Length;
            int m = t.Length;
            var d = new int[n + 1, m + 1];

            // Step 1
            if (n == 0)
            {
                return m;
            }

            if (m == 0)
            {
                return n;
            }

            // Step 2
            for (int i = 0; i <= n; d[i, 0] = i++)
            {
            }

            for (int j = 0; j <= m; d[0, j] = j++)
            {
            }

            // Step 3
            for (int i = 1; i <= n; i++)
            {
                //Step 4
                for (int j = 1; j <= m; j++)
                {
                // Step 5
                int cost = (t[j - 1] == s[i - 1]) ? 0 : 1;

                // Step 6
                d[i, j] = Math.Min(
                    Math.Min(d[i - 1, j] + 1, d[i, j - 1] + 1),
                    d[i - 1, j - 1] + cost);
                }
            }
            // Step 7
            return d[n, m];
            }

提前致谢!

Hi and thanks for looking!

Background

I have a computing task that requires either a lot of time, or parallel computing.

Specifically, I need to loop through a list of about 50 images, Base64 encode them, and then calculate the Levenshtein distance between each newly encoded item and values in an XML file containing about 2000 Base64 string-encoded images in order to find the string in the XML file that has the smallest Lev. Distance from the benchmark string.

A regular foreach loop works, but is too slow so I have chosen to use PLINQ to take advantage of my Core i7 multi-core processor:

Parallel.ForEach(candidates, item => findImage(total,currentWinner,benchmark,item));

The task starts brilliantly, racing along at high speed, but then I get an "Out of Memory" exception.

I am using C#, .NET 4, Forms App.

Question

How do I tweak my PLINQ code so that I don't run out of available memory?

Update/Sample Code

Here is the method that is called to iniate the PLINQ foreach:

private void btnGo_Click(object sender, EventArgs e)
{
    XDocument doc = XDocument.Load(@"C:\Foo.xml");
    var imagesNode = doc.Element("images").Elements("image"); //Each "image" node contains a Base64 encoded string.
    string benchmark = tbData.Text; //A Base64 encoded string.
    IEnumerable<XElement> candidates = imagesNode;

    currentWinner = 1000000; //Set the "Current" low score to a million and bubble lower scores into it's place iteratively.
    
    Parallel.ForEach(candidates, i => {
        dist = Levenshtein(benchmark, i.Element("score").Value);
        if (dist < currentWinner)
        {
            currentWinner = dist;
            path = i.Element("path").Value;
        }
    });
}

. . .and here is the Levenshtein Distance Method:

public static int Levenshtein(string s, string t)    {
            int n = s.Length;
            int m = t.Length;
            var d = new int[n + 1, m + 1];

            // Step 1
            if (n == 0)
            {
                return m;
            }

            if (m == 0)
            {
                return n;
            }

            // Step 2
            for (int i = 0; i <= n; d[i, 0] = i++)
            {
            }

            for (int j = 0; j <= m; d[0, j] = j++)
            {
            }

            // Step 3
            for (int i = 1; i <= n; i++)
            {
                //Step 4
                for (int j = 1; j <= m; j++)
                {
                // Step 5
                int cost = (t[j - 1] == s[i - 1]) ? 0 : 1;

                // Step 6
                d[i, j] = Math.Min(
                    Math.Min(d[i - 1, j] + 1, d[i, j - 1] + 1),
                    d[i - 1, j - 1] + cost);
                }
            }
            // Step 7
            return d[n, m];
            }

Thanks in advance!

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

勿挽旧人 2025-01-01 12:13:21

更新

今天在不同情况下再次遇到此错误。我正在开发一个内存需求较高的桌面应用程序。确保您已将项目设置为 64 位架构以访问所有可用内存。我的项目默认设置在 x86 上,因此我不断出现内存不足的异常。当然,只有当您的部署可以依靠 64 位处理器时,这才有效。

结束更新

经过一番努力后,这似乎是操作员错误:

我从并行线程调用 UI 线程以更新进度标签,但我没有以线程安全的方式执行此操作。

此外,我在没有调试器的情况下运行应用程序,因此每次代码尝试从并行线程更新 UI 线程时都会出现未捕获的异常,从而导致溢出。

虽然不是 PLINQ 方面的专家,但我猜测只要您不犯像这样的愚蠢的臭代码错误,它就会为您处理所有低级分配的内容。

希望这对其他人有帮助。

Update

Ran into this error again today under different circumstances. I was working on a desktop app with high memory demand. Make sure that you have set the project for 64-bit architecture to access all available memory. My project was set on x86 by default and so I kept getting out of memory exceptions. Of course, this only works if you can count on 64-bit processors for your deployment.

End Update

After struggling a bit with this it appears to be operator error:

I was making calls to the UI thread from the parallel threads in order to update progress labels, but I was not doing it in a thread-safe way.

Additionally, I was running the app without the debugger, so there was an uncaught exception each time the code attempted to update the UI thread from a parallel thread which caused the overflow.

Without being an expert on PLINQ, I am guessing that it handles all of the low-level allocation stuff for you as long as you don't make a goofy smelly code error like this one.

Hope this helps someone else.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文