VectorStyler
    • Categories
    • Unread
    • Recent
    • Tags
    • Popular
    • Register
    • Login

    Speeding up the workflow in VS

    Scheduled Pinned Locked Moved Questions and Support
    2 Posts 2 Posters 2.9k Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • BoldlineB Online
      Boldline
      last edited by Boldline

      Is there a way to speed up the tasks in VS? Each action whether selecting nodes or moving them or making selections, they all literally take a second or two before they register. It's difficult to get things done when I'm waiting for VS to catch up on each step of the process.
      This is not a specific build issue, it's been this way over several builds. I have an M1 mac mini with 16GB of ram . VS is consistently using between 1.7GB and 2 GB or RAM at any given time. I've tried shutting down other apps that might be draining ram from VS...

      Edit: Clearing the history panel helps a lot - speed has improved considerably since I cleared the hisotry so maybe that is my main issue?

      I started closing out several open VS file tabs and then VS force quitted on me before I could close the rest. Since reopening, VS has been faster - I just wonder hy it force-quit. I did not get the VS crash log dialoge box, but I got the apple one

      🍎 macOS Tahoe 26.2, Mac mini (M1, 2020), Chip Apple M1, Memory 16 GB
      Cintiq 27QHD Display and LG Ultra HD Display

      VectorStylerV 1 Reply Last reply Reply Quote 0
      • VectorStylerV Offline
        VectorStyler @Boldline
        last edited by

        @Boldline said in Speeding up the workflow in VS:

        they all literally take a second or two before they register

        I think this could be a bug. And the force quit too.
        The 1.7 - 2 GB RAM usage seems normal on M1. Should start out around 800MB and then gradually accumulates some caches.
        But this does not affect the performance (caching actually improves it).

        Some other thing might cause this. I add this to the backlog.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post