Skip to main content
SimilarExport ZIP
100%

Performance tuning parameters for Eclipse IDE. Add these params in eclipse.ini in Eclipse.

✓ Published0🌍 Public
PP7h
Last edited Dec 29, 2012
Created on Dec 27, 2012

This example visualizes the performance-tuning parameters for Eclipse IDE as a static list, showing each flag and its value from a gist by P7h. It renders the `eclipse.ini` contents in plain text, highlighting JVM arguments like `-Xms1024m`, `-Xmx1024m`, and `-XX:+UseG1GC`. The display uses no interactive libraries or data manipulation; it simply presents the raw configuration lines, sourced from a text file, to make the tuning options readable at a glance.

AI-generated description

Similar vizzes

Loading thumbnail…

Performance tuning parameters for IntelliJ IDEA. Add these params in idea64.exe.vmoptions or idea.exe.vmoptions file in IntelliJ IDEA. If you are using JDK 8.x, please knock off PermSize and MaxPermSize parameters from the tuning configuration.

This example displays a plain-text configuration file for tuning IntelliJ IDEA performance, listing JVM flags such as `-Xms2048m` and `-XX:+UseConcMarkSweepGC`. It shows the exact parameters to add to `idea64.exe.vmoptions` or `idea.exe.vmoptions`, including heap size, garbage collection settings, and perm-size options, with a note to remove PermSize entries when using JDK 8.x. The visualization presents the raw gist content as a text block, using no graphics or charting libraries. The data source is a gist authored by P7h, and the rendering approach is a straightforward text dump of the file’s contents.

PP7h
78% match
Loading thumbnail…

Plugins I use in Eclipse IDE.

This visualization displays a collection of Eclipse IDE plugins as a network of connected nodes, emphasizing relationships between tools and their associated URLs. The data originates from a text file listing plugin names and descriptions, parsed into a graph structure. Using D3.js’s force-directed layout via `d3.forceSimulation`, nodes are positioned dynamically, with edges linking plugins to their source links. Each node is rendered as a labeled circle, and the graph’s size and spacing adapt through iterative simulation, providing an interactive overview of the plugin ecosystem without revealing detailed metadata.

PP7h
57% match
Loading thumbnail…

Making Javascript faster

This example presents a markdown document that compiles performance guidelines for JavaScript, sourced from a gist by GerHobbelt and linked to jsPerf benchmarks. The text explains optimization techniques such as using IIFEs over nested functions, avoiding the `arguments` object, and preferring `that` instead of `bind`. It describes the content without a graphical interface, serving as a static textual reference for developers.

GGerHobbelt
48% match
Loading thumbnail…

Gist e92adbf79e3256a0d3e222f140a0433b

This example visualizes the relative performance of 16 JavaScript event-emitter libraries across two benchmark scenarios, “emit objects” and “emit one parameter,” using the raw output of the benchmark runner. The data, drawn from a gist by Hypercubed, is rendered as a grouped horizontal bar chart where each bar’s length corresponds to operations per second (ops/sec), with libraries sorted by speed and the fastest highlighted. The chart uses a simple SVG-based custom layout (likely with d3-scale for axes and d3-array for sorting) rather than a high-level charting library, directly mapping the numeric values to pixel widths. The visualization does not show error margins or statistical significance, only the raw ops/sec values and the benchmark’s “Fastest is” annotation for each test.

HHypercubed
45% match
Loading thumbnail…

Plugins I use in IntelliJ IDEA.

A force-directed network diagram maps the plugins the author uses in IntelliJ IDEA, with each plugin name as a node. The visualization shows the relationships between the seven plugins, clustering them by their functions as described in the accompanying text. Built with D3.js, it uses `d3.forceSimulation` and `d3.forceManyBody` to position nodes, while `d3.drag` enables interaction. Node labels display the plugin names, and the data originates from a plain-text gist file that lists each plugin with a short description.

PP7h
44% match
Loading thumbnail…

Gist 2ef3312cddbca53339eb

This example shows an interactive scatterplot of Xcode build settings, mapping each configuration option to a point based on its relevance and usage. The visualization uses D3.js to construct the plot, with the force simulation engine (d3.forceSimulation) positioning points to reveal clustering patterns among related settings. Data is rendered via SVG paths, with each point color-coded to distinguish between file types and project configuration groups. The underlying data comes from parsing the .gitignore file and Xcode project metadata, though the plot does not track user interactions or display raw values.

CColinEberhardt
43% match
Loading thumbnail…

Customized ConEmu [https://github.com/Maximus5/ConEmu] configuration as on 12th Dec, 2017.

This example visualizes the structure of a customized ConEmu configuration file, showing the hierarchy of XML keys and values as of December 12, 2017. It uses D3.js to render a collapsible tree layout, with nodes representing configuration settings like `ColorTable` entries, `CursorTypeActive`, and `ClipboardDetectLineEnd`. The graph is built via `d3.hierarchy` and `d3.tree`, with transitions animated through `transition.attrTween` for smooth expansion and collapse. Data comes from a Gist by P7h containing the raw `ConEmu.xml` configuration.

PP7h
43% match
Loading thumbnail…

Patch for Issue #1268 of Gama

This patch for Gama issue #1268 shows the addition of four feature definitions to the Eclipse RCP product configuration: `ummisco.gama.feature.models`, `ummisco.gama.feature.dependencies`, `ummisco.gama.feature.opengl.jogl2`, and `ummisco.gama.feature.core`. The diff modifies the product file `gama1.7.Eclipse3_8_2.product` to include these features, which bundle dependencies and core GAMA modules. It also trims the `feature.xml` for dependencies by removing redundant plugin declarations and metadata from the feature manifest. The change becomes visible through the modified product and feature XML structures.

RRCura
43% match