Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • in reply to: Some Sqlyog Questions #24624

    Thanks Peter,

    Just to make sure that I understood what you said regarding multithreading,

    If I open one or more “Query Tabs”, there will be one thread executing the queries for each of the 'Query Tab'. Also, all the queries in a single query tab will be executed by a single thread sequentially. Does SQLYog create a new session for each of the query tab(or thread)?

    Thanks,

    Tushar.

    peterlaursen wrote on Aug 7 2007, 09:23 PM:
    1) the meaning is that you can have more connectsons open at the same time (to the same or different servers) and those different connections operate indepedently. If you enter more queries in the editor (or execute a script with more queries) they will of course execute sequentially. For HTTP-connections only a new connection is created for every query (due to the nature of PHP). Additional connections are created in the background for the 'autocomplete feature' and for certain copy operations.

    Was that the answer?

    2) We have plans for internationalisation. How many languages we will support officially and when is not decided in detail yet.

    Please refer to:

    http://webyog.com/faq/content/33/20/en/pla…-of-sqlyog.html

    The current plans are: version 6.1 will ship with a Visual Schema Designer, version 6.2 with 'FORMS' (keyboard friendly data entry feature). Also a lot of smaller issues will be adressed in those releases. After that (about 3 months is my best guess) we have not decided on priorities yet.

    3) Currently it does not: when physcial + virtual memory is filled up it is likely to crash. We know this but it is not very easy to handle actually – and I think every GUI database client does the same! We will provide manual STOP options everywhere where it still does not exist in near future (planned for 6.1).

    in reply to: Some Questions About Monyog #24621

    Thanks for the reply Sabyasachi, much appreciated.

    Regarding the graphs, I was just wondering if it was possible to use our own metrics there instead of time e.g. say select_scan plotted against the number of queries that may give an insight into how good our indexing system is.

    One more question regarding MONYog, if you dont mind 🙂

    Does MONyog support internationalization now? If not, do you guys have any plans to provide it in the near future?

    Regards,

    Tushar.

    Sabyasachi Ruj wrote on Aug 7 2007, 05:24 PM:
    Thanks for trying MONyog!

    All the graphs in dashboard interface are plotted against time. And they are last fifteen collected data.

    Currently it is not possible to plot any graph against something except time.

    But we would like to know your request/doubt in more detail.

    Can you give one example of what do you want in the graphs?

    MONyog reads “/proc” file system in Linux systems to collect system related values.

    Yes it displays the memory information. Of-course, the target system (which you are monitoring) has to be Linux based.

    I am discussing the system related MONyog Object Model(MOM) below:

    There are four system related categories in MOM. They are:

    Physical Memory related:


    All these physical memory related metrics gives the values in KB.

    “MONyog.System.Mem.sys_mem_total” : Total physical memory.

    “MONyog.System.Mem.sys_mem_free” : Available physical memory.

    “MONyog.System.Mem.proc_mem_vmrss” : Physical memory being used by MySQL.

    Swap memory related:


    All these swap memory related metrics gives the values in KB.

    “MONyog.System.Swp.sys_swp_total” : Total swap memory.

    “MONyog.System.Swp.sys_swp_free” : Free Swap memory.

    “MONyog.System.Swp.proc_swp_vmsize” : Swap memory being used by MySQL.

    CPU related:


    All these CPU related metrics give the number of jiffies spent in various modes, since the last capture.

    “MONyog.System.Cpu.sys_cpu_user” : User mode

    “MONyog.System.Cpu.sys_cpu_nice” : Nice mode

    “MONyog.System.Cpu.sys_cpu_system” : System/Kernel mode

    “MONyog.System.Cpu.sys_cpu_idle” : Spent Idly

    “MONyog.System.Cpu.sys_cpu_iowait” : Spent in waiting for IO

    “MONyog.System.Cpu.sys_cpu_hi” : Spent in hardware interrupts

    “MONyog.System.Cpu.sys_cpu_si” : Spent in Software interrupts

    Custom:


    “MONyog.System.Custom.Available” : If the system is available to MONyog or not.

    Currently you can monitor only “Availability”, other CPU and Memory.

    NOTE:

    —-

    Please note that, currently “Timeframe” does not have any effect on system related values.

Viewing 2 posts - 1 through 2 (of 2 total)