Korean text rendering

[Sung-Jae, Cho]

>  I almost sure already this is Intel HD 620 graphics not enough for
Koreans :)

I think that's also good hardware still.

And next test is done with Intel N2840 Celeron notebook with 4 GB
RAM, SATA3 SSD.
It's not exactly same with Intel HD620 Graphic core, but it was produced
with Ivy Bridge based Atom SoC processor, and it has HD Graphic core too.
As you know, HD Graphic core shared with main memory area, it is related
with BIOS, driver and Memory health.

In my test case, it works well.
(Almost same or faster than in the clip.)

I'm sorry for your experience.

I think if there are problems, storage I/O (SSD or HDD) or memory bandwidth.
If you feel Asian characters rendering is slower than other fonts, it is
related to memory bandwidth.
I know more load is needed to render asian fonts. But that's not a problem
after Core i series and amd64 CPU systems with SSD.
KDE framework, Qt framework, font cache systems are not a problem.
It's fair from this problem.

Could you check your  system health check with memtest86 or
gnome-disk-utility?


On Thu, May 15, 2025 at 6:22 PM Igor Mironchik <igor.mironchik at gmail.com>
wrote:

> Hi.
>
> I almost sure already this is Intel HD 620 graphics not enough for Koreans
> :)
>
> But I wait for test on your side.
>
> Thank you.
> On 15.05.2025 12:02, Sung-Jae, Cho wrote:
>
> Hi, again.
>
> First test is done with Virtual Box.
> I captured a video and please check the clip below.
>
> https://drive.google.com/file/d/1WXl4CxMv1iNkO72F_5uXnLyOGVG33ytA/view?usp=sharing
> I think it is not much delayed.
> After installing OpenSuse tumbleweed, I added ibus-hangul package with
> ibus-daemon, google-noto-sans-kr fonts.
> Maybe it is related to the graphic card driver, on the next installing
> notebook with HD620 graphic core.
>
> On Thu, May 15, 2025 at 5:15 PM Sung-Jae, Cho <cho.sungjae at gmail.com>
> wrote:
>
>> Thanks for the information. :)
>>
>> Additionally, I'll test with an Intel HD Graphics 620 notebook, too.
>>
>> On Thu, May 15, 2025 at 5:09 PM Igor Mironchik <igor.mironchik at gmail.com>
>> wrote:
>>
>>> On 15.05.2025 10:44, Sung-Jae, Cho wrote:
>>>
>>> I'll try again with openSUSE Tumbleweed. :)
>>> Please, wait a day. I'll try with virtual machines and real machines,
>>> both.
>>> And if you can bring some hardware information with a video card driver,
>>> xorg-driver, etc,
>>> it'll be helpful for finding the cause.
>>>
>>> Operating System: openSUSE Tumbleweed 20250512 KDE Plasma Version: 6.3.5
>>> KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Kernel Version:
>>> 6.14.5-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel®
>>> Core™ i5-7200U CPU @ 2.50GHz Memory: 7,6 GiB of RAM Graphics Processor:
>>> llvmpipe Manufacturer: HP Product Name: HP ProBook 640 G3
>>>
>>> Extended renderer info (GLX_MESA_query_renderer):
>>>
>>> Vendor: Intel (0x8086)
>>>
>>> Device: Mesa Intel(R) HD Graphics 620 (KBL GT2) (0x5916)
>>>
>>> Version: 25.0.5
>>>
>>> Accelerated: yes
>>>
>>> Video memory: 3909MB
>>>
>>> Unified memory: yes
>>>
>>> Preferred profile: core (0x1)
>>>
>>> Max core profile version: 4.6
>>>
>>> Max compat profile version: 4.6
>>>
>>> Max GLES1 profile version: 1.1
>>>
>>> Max GLES[23] profile version: 3.2
>>>
>>> OpenGL vendor string: Intel
>>>
>>> OpenGL renderer string: Mesa Intel(R) HD Graphics 620 (KBL GT2)
>>>
>>> OpenGL core profile version string: 4.6 (Core Profile) Mesa 25.0.5
>>>
>>> OpenGL core profile shading language version string: 4.60
>>>
>>> OpenGL core profile context flags: (none)
>>>
>>> OpenGL core profile profile mask: core profile
>>>
>>> EGL driver name: iris
>>>
>>> EGL_MESA_image_dma_buf_export, EGL_MESA_query_driver,
>>>
>>> EGL driver name: iris
>>>
>>> EGL_MESA_gl_interop, EGL_MESA_image_dma_buf_export,
>>> EGL_MESA_query_driver,
>>>
>>> EGL driver name: iris
>>>
>>> EGL_MESA_image_dma_buf_export, EGL_MESA_query_driver,
>>>
>>> EGL driver name: iris
>>>
>>> EGL_MESA_image_dma_buf_export, EGL_MESA_query_driver,
>>>
>>> EGL driver name: swrast
>>>
>>> EGL_MESA_image_dma_buf_export, EGL_MESA_query_driver,
>>>
>>>
>>> On Thu, May 15, 2025 at 4:38 PM Igor Mironchik <igor.mironchik at gmail.com>
>>> wrote:
>>>
>>>>
>>>> On 15.05.2025 08:49, Konstantin Kharlamov wrote:
>>>> > On Thu, 2025-05-15 at 08:37 +0300, Igor Mironchik wrote:
>>>> >> On 15.05.2025 08:29, Konstantin Kharlamov wrote:
>>>> >>> On Thu, 2025-05-15 at 06:29 +0300, Igor Mironchik wrote:
>>>> >>>> Hi.
>>>> >>>>
>>>> >>>> Are any Korean here? I'm curious if they have very bad
>>>> >>>> performance of
>>>> >>>> rendering Korean text in any Qt application? Or is this just
>>>> >>>> because
>>>> >>>> of
>>>> >>>> missing some fonts on my system? I see a huge performance
>>>> >>>> slowdown on
>>>> >>>> Korean text rendering.
>>>> >>> How did you measure? I'm not a Korean, but I tried pasting a Korean
>>>> >>> wiki article to Kate with "Droid Sans [1ASC]" font and scrolling
>>>> >>> and I
>>>> >>> don't see any change in performance. Perhaps some more scientific
>>>> >>> method required.
>>>> >>
>>>> >> I paste in Kate a Korean text (~1kB), it took so much time to paste
>>>> >> and
>>>> >> render it (~5 seconds), and Kate starts to think a lot even on
>>>> >> navigating in menu.
>>>> >>
>>>> >> The same with English or Russian text - I don't see any delays, Kate
>>>> >> is
>>>> >> responsive.
>>>> > I see. Seems something specific to your system — I just created a 158K
>>>> > text file by copy-pasting a Korean Wiki article a dozen of times, and
>>>> > when I open it in Kate, everything is smooth and nice.
>>>> >
>>>> > Is it maybe the font? What font do you use? Can you try going to Kate
>>>> > settings and changing the font to "Droid Sans [1ASC]" (on Archlnux
>>>> it's
>>>> > a `ttf-droid` package) and seeing if that makes any difference?
>>>>
>>>> I guess too this is system specific. I'm on openSUSE Tumbleweed.
>>>> Changing editor's font to Droid Sans doesn't help.
>>>>
>>>> Ok. I see that this issue is system specific, so my question is
>>>> answered. Maybe somebody can check this issue on Tumbleweed only?
>>>>
>>>> Thank you.
>>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20250515/0fc65d44/attachment.htm>