Hi Rony,

Have you monitored the memory usage while running the test? In the cases I have 
had similar problem it have invariantly been lack of physical memory and the 
machine starting to swap out memory to disk.

If you like I can run the test tomorrow on a machine with lots of memory. Just 
let me know how to run it if there are special conditions

Hälsningar/Regards/Grüsse,
P.O. Jonsson
[email protected]




> Am 03.01.2026 um 20:36 schrieb Rony G. Flatscher <[email protected]>:
> 
> In 
> <https://sourceforge.net/p/oorexx/discussion/general/thread/e0fc468371/?limit=25#5211/a31a/19b6/70b7/00a8>
>  
> <https://sourceforge.net/p/oorexx/discussion/general/thread/e0fc468371/?limit=25#5211/a31a/19b6/70b7/00a8>
>  a problem with reading JSON data with json.cls was reported.
> 
> The enclosed "test.rex" creates two JSON files, one (test_01.json, 2.8 MB) 
> with an array of 90.000 directory objects, one (test_02.json, 5.7 MB) with an 
> array of 180.000 directory objects. It then reads the JSON files twice and 
> creates the respective ooRexx array containing 90.000 or 180.000 directory 
> objects with one entry ("Index n" with "Value n", where n=1 ... 
> 90.000|180.000).
> 
> Here the timings on an older machine:
> 
> G:\test\orx\json\perf\take2>test
> created test_01.json: 00:00:00.041000
> wrote test_01.json: 00:00:00.003000
> created test_02.json: 00:00:00.087000
> wrote test_02.json: 00:00:00.005000
> ---
> importing test_02.json ...
> importing test_02.json lasted: 00:01:10.770000
> test_02.json: res~items: 180000
> importing test_02.json ...
> importing test_02.json lasted: 00:06:03.864000
> test_02.json: res~items: 180000
> importing test_01.json ...
> importing test_01.json lasted: 00:02:15.433000
> test_01.json: res~items: 90000
> importing test_01.json ...
> importing test_01.json lasted: 00:00:43.929000
> test_01.json: res~items: 90000
> Repeating reading test_02.json lasts appr. five (!) times longer (01:10.770 
> vs. 06:03.864 minutes)! Also reading the first time test_01.json lasts five 
> times longer than the second time (02:15.433 vs. 00:43.929). Also, the latest 
> "json.cls" is enclosed (committed to trunk today), which seems to be able to 
> read almost twice as fast as the release version (test.rex was carried out 
> with the enclosed version of json.cls). 
> 
> Now, the test data did not change, the code did not change, so it is strange 
> that such a big variation can be observed (unless I miss something obvious). 
> 
> So maybe there is some heavy effect on ooRexx creating 180.000 (90.000) 
> directory objects and storing them in an array?
> 
> What might be the reason? What can be done about it?
> 
> ---rony
> 
> 
> <json.cls><test.rex>_______________________________________________
> Oorexx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to