实时应用程序中的 JRuby、大型数组和性能问题

发布于 2024-11-05 23:57:11 字数 1266 浏览 0 评论 0原文

我正在开发一个实时游戏应用程序。其中大部分是用 Java 编写的，但最近我决定尝试将一些初始化过程移至 JRuby 脚本中，以便最大限度地方便玩家修改世界的生成方式。

首先，我决定将地图生成转移到 JRuby 脚本中。目前，这可以归结为以下 Java 代码：

ScriptingContainer container = new ScriptingContainer();
container.put("$data", dataPackage);
container.runScriptlet(PathType.RELATIVE, scriptName);
dataPackage = (BlockMapGenerationDataPackage)container.get("$data");

数据包包含 Java 程序生成最终地形并渲染它所需的所有信息，并且还包含 Ruby 脚本能够生成所需的数据。制作各种地图。特别是，它包含一个相当大的数组（当前为 1000 x 1000 x 15）。为了测试 Ruby 脚本是否正常工作，我去掉了整个地图生成算法，并进行了以下极其简单的测试：

require 'java'
Dir["../../dist/\*.jar"].each { |jar| require jar }

for i in (0...$data.getWidth())
  for j in (0...$data.getDepth())
    $data.blocks[i][j][0] = Java::BlockMap::BlockType::GRASS
  end
end

该测试仅在初始化时执行一次。现在，当这一切都用 Java 实现时，使用更多的内存密集型生成算法，就不存在任何类型的性能或内存问题。该游戏在具有 1000 x 1000 x 15 地图的旧笔记本电脑上以每秒数百帧的速度以非常高的分辨率流畅运行。然而，当 Java 生成代码被上述 JRuby 脚本替换时，该程序似乎遇到了一些内存消耗问题：帧速率下降了约 30-40 fps，并且程序在令人印象深刻的一致情况下冻结了十分之一秒。大约每三秒一次的周期性频率。分析和各种测试表明，唯一可能的罪魁祸首是 Ruby 脚本。

此外，如果地图的尺寸大幅减小，比如缩小到 100 x 100 x 15，那么这些问题或多或少就会消失。

我尝试过各种方法，例如在 Java 代码之后添加 container.terminate(); 或 container.clear(); 来执行脚本，但我真的不这样做了解问题的根源或如何解决它。如果有人能解释这里出了什么问题以及是否可以解决这个问题，我将不胜感激！

原文

I'm working on a real-time game application. Most of it is written in Java, but recently I decided to experiment with moving some of the initialization procedures into JRuby scripts in order to maximize the ease for the player to modify how the world is generated.

As a start, I decided to move the map generation into a JRuby script. At present, this boils down to the following Java code:

ScriptingContainer container = new ScriptingContainer();
container.put("$data", dataPackage);
container.runScriptlet(PathType.RELATIVE, scriptName);
dataPackage = (BlockMapGenerationDataPackage)container.get("$data");

The data package contains all the information necessary for the Java program to produce the final terrain and render it, and it also contains the necessary data in order for the Ruby script to be able to craft all manner of maps. In particular, it contains a rather large array (currently 1000 x 1000 x 15). To test whether the Ruby script was working, I've stripped out the entire map generation algorithm and put in the following extremely simple test:

require 'java'
Dir["../../dist/\*.jar"].each { |jar| require jar }

for i in (0...$data.getWidth())
  for j in (0...$data.getDepth())
    $data.blocks[i][j][0] = Java::BlockMap::BlockType::GRASS
  end
end

This is executed only once upon initialization. Now when this was all implemented in Java, with far more memory intensive generation algorithms, there were no performance or memory issues of any kind. The game ran smoothly at hundreds of frames per second at very high resolutions on an old laptop with a 1000 x 1000 x 15 map. However, when the Java generation code is replaced by the above JRuby script, the program appears to suffer some memory consumption issues: the frame rate drops by about 30-40 fps and the program freezes for maybe a 10th of a second at an impressively consistent periodic rate of about once every three seconds. Profiling and various tests reveal that the only possible culprit is the Ruby script.

Moreover, if the size of the map is drastically reduced, say to 100 x 100 x 15, then these issues more or less disappear.

I've tried various things like adding container.terminate(); or container.clear(); after the Java code to execute the script, but I really don't understand the source of the issue or how to fix it. I'd greatly appreciate if someone could explain what's going wrong here and whether or not this can be fixed!

分享到QQ

分享到微博