Jump to content
adrian

Tracy Debugger

Recommended Posts

Remember that if you are a superuser and you have "force su into dev mode" checked, then switching modes won't affect the mode you actually see. How is the performance when you are logged out?

Tracy adds content to the DOM, so it should slow things down if anything. 

Is Tracy logging any errors (even Notices / Warnings)? Do you have any ajax calls - just wondering if Tracy is catching an error early that would otherwise slow things down for some reason?

Are you talking about  the backend or the frontend of the site being slow? Are they both slow with Tracy disabled?

Does Tracy still speed things up with all panels disabled? If not, which particular panel is increasing the speed?

 

Share this post


Link to post
Share on other sites

"force su into dev mode" is not checked and there are no errors or warnings

I didn't checked all panels, but It's enough to add one of them: ProcessWire Info or Request Info or Console or Panel Selector.

It's not speeding up with i.e. Tracy Logs or ProcessWire Logs

Backend works normal exept the pagetree. pagetree takes longer than usual.

Share this post


Link to post
Share on other sites

Another interessting thing is that the frontend seems to slow down only when logged in as superuser. For guests the Site seems to work normal.

Share this post


Link to post
Share on other sites
1 minute ago, Kholja said:

Another interessting thing is that the frontend seems to slow down only when logged in as superuser. For guests the Site seems to work normal.

Is this speed affected by Tracy at all? Keep in mind that PW's core debug mode kicks in (if it's enabled) when logged in as superuser so there will be some impact from that.

33 minutes ago, Kholja said:

I didn't checked all panels, but It's enough to add one of them: ProcessWire Info or Request Info or Console or Panel Selector.

It's not speeding up with i.e. Tracy Logs or ProcessWire Logs

I honestly have no idea at this point - I can't see why/how those panels could improve the page tree loading speed - for me the page tree ajax call is definitely noticeably slower with Tracy running - obviously it's a trade-off that I think is worth it though.

Share this post


Link to post
Share on other sites
2 minutes ago, adrian said:

Is this speed affected by Tracy at all? Keep in mind that PW's core debug mode kicks in (if it's enabled) when logged in as superuser so there will be some impact from that.

Definitely it affects the Frontend. I think a difference by factor about 20 (300ms -> 6s server response time) is probably not caused by the core. In terms of the backend I'm not sure if I'm starting to see ghosts... the impact there is not that big.
Anyway - thanks for your precious input adrian. If i find out more I will post it here.

Share this post


Link to post
Share on other sites
7 minutes ago, Kholja said:

Definitely it affects the Frontend. I think a difference by factor about 20 (300ms -> 6s server response time)

Is this on all pages or just pages of certain templates?

 

Share this post


Link to post
Share on other sites

It's affecting all templates. I created a test template with only a few fields. It has the same bad performance.

Share this post


Link to post
Share on other sites

I exported the site with ryans ProcessExportProfile Module and did a fresh install. This solved the problem. But would be nice to know what caused the issue.
Thanks Adrian for your quick  response and your support. Your posts were often helpful und a good resource for learning 🙂

  • Like 1

Share this post


Link to post
Share on other sites
3 hours ago, Kholja said:

I exported the site with ryans ProcessExportProfile Module and did a fresh install. This solved the problem. But would be nice to know what caused the issue.

Weird - definitely keep us up to date if you find out why.

Share this post


Link to post
Share on other sites
On 2/10/2020 at 8:49 AM, bernhard said:

Thx, I'm done with my testing - asking earlier would have saved me some hundred clicks 😄 😛


$options[Dumper::COLLAPSE] = 14;
$options[Dumper::COLLAPSE_COUNT] = 7;

This worked well. It would be nice to have an option somewhere for this, but it is definitely not high priority, so don't hurry. Thx anyhow for taking it into account! 🙂 

Hey @bernhard - those are now the defaults (as per the Tracy core defaults). They are also configurable in the module settings:

image.thumb.png.279d2ad1eead8e148568c28f834575c2.png

and you can also override them for a specific dump with:

d($obj, 'title', ['collapse' => 1, 'collapse_count' => 1]);

which might be handy if you are dumping lots of the same object/array in a loop and you don't want them all open which not only takes up more physical space, but also more reources.
 

  • Like 2

Share this post


Link to post
Share on other sites

Just dumping a note here for others. If anyone notices slowness with Tracy enabled, especially when quite a few modules are active, try using php-fpm. I just switched my local set up of homebrew apache + homebrew php 7.4 over to php-fpm instead of mod_php and it has really sped things up. Also been mucking around with the database for the site I am working on, didnt realise I was on MyISAM, so maybe switching to INNODB has had something to do with it as well.

Share this post


Link to post
Share on other sites

Does anybody know the keyboard shortcut for the multi-cursor feature of ACE? I'm using CTRL-D in VSCode but that does delete the current line in ACE. Multicursor does work though, because I can select multiple items using CTRL+click. Thx!

Share this post


Link to post
Share on other sites

Is ACE Tracy's console editor? If so, then ALT-GR works for me (Windows).

Share this post


Link to post
Share on other sites
30 minutes ago, bernhard said:

Does anybody know the keyboard shortcut for the multi-cursor feature of ACE?

CTRl or CMD + click where you want each extra cursor to be.

Oops, sorry, I guess you already mentioned you had this approach working 🙂

Share this post


Link to post
Share on other sites

I'm sorry, I was not precise enough! 😅 See this example:

3WVbDyG.png

The cursor is on the first $out variable and all other occurrances are outlined, so I guess there is a way to select all of them (VSCode CTRL+F2) or one by one (VSCode CTRL-D). This is how it looks in VSCode:

OsUz7Wp.gif

Share this post


Link to post
Share on other sites

In ACE Editor (on a Mac at least), you can do this sort of stuff by using CTRL+ALT + Arrow Down (or Up). Does that do what you want?

UdwJQhutMI.gif.a8011691523abcb524d7efb84f28c1d8.gif

8b4ySpjkEY.gif.978b68768fb0b94a5e5e3dae42699577.gif

Share this post


Link to post
Share on other sites

Thank you very much adrian, not exactly, because that won't work on the last line where $out is prepended by "d(". But I found a list of shortcuts 🙂 https://defkey.com/ace-editor-shortcuts

It's CTRL-ALT-left/right

Not sure if that is an official list, but it might be nice adding a link to the console or inside the keybord shortcuts popup?

QfT2GYL.png

Share this post


Link to post
Share on other sites

Great! Yeah I just did a quick websearch and my link was the first result 🙂 

Share this post


Link to post
Share on other sites

@bernhard - I've added that link to the keyboard shortcuts dialog in the latest version. I've also added that dialog to the FileEditor panel.

image.png.ca5f74e7a1e18366564f843013a6afe8.png

  • Thanks 1

Share this post


Link to post
Share on other sites

Great, thank you adrian! I hope it also helps others 🙂 

  • Like 1

Share this post


Link to post
Share on other sites

Just had to look something up in the Tracy Docs and found their donation button 🙂 So if anybody wants to thank the guys behind Tracy, here's the link: https://nette.org/en/make-donation?to=tracy

Can't thank you enough (Adrian and the guys from Nette) for this awesome tool!

  • Like 2

Share this post


Link to post
Share on other sites

@adrian could you please add the name of the field in the admin actions panel so that it is more obvious and secure?

J5sIDjX.png

Here I'm deleting the field "summary" but it looks more like I am deleting the field "Text". A simple "Delete field > summary < " would do. I think it's a little dangerous as it is now - it's common to have many tabs open at the same time, so there's a high risk of clicking that button in the wrong tab accidentally.

Thank you 🙂 

  • Like 1

Share this post


Link to post
Share on other sites

Hey @bernhard - sure thing. I did the same for template deletion as well.

  • Like 1

Share this post


Link to post
Share on other sites

Just a quick note that the latest release fixes the "NEW SINCE" feature in the API Explorer panel. It had always mostly seemed to work, but I was often seeing results from old upgrades but wasn't sure why. I think it's now fixed, but I'd appreciate if you guys could check at your end when you next upgrade the PW core and see if it appears correct for you as well. Thanks.

  • Like 3

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Pip
      Hi everyone!
      I'm trying out the Login/Register module for my site. Noted that the module assigns the newly registered user to login-register role. 
      Once you modify the login-register role's permissions, particularly adding page-edit, the new member role will be set to guest. 
      Thing is I'd like to grant my new users the power to create their own pages. Any advice? 
      Thanks. 
    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
×
×
  • Create New...