PyScripter is easily the best IDE I have come across for interactive work - especially with its ability to connect to remote engines.
It allows me to open multiple instances of pyscripter, each is tied to a different version (I have 3.3, 2.7 64 bit and 32 bit on my machine).
Question: Can I open multiple instances of pyscripter tied to 2.7 64 bit? Would help m enormously as I have huge amounts of ram and could easily work on two or three projects at a time.
Going to the command prompt and requesting PyScripter -N gives me a new instance as suggested at
[https://groups.google.com/forum/?fromgroups=#!topic/pyscripter/0ebFUx6h7Z4][1]
, but it seems to default to 3.3 - but does open multiple instances of 3.3. I am not to familiar with how PyScripter picks out which version of python to tie to. Any help is most appreciated!
Update:
Removing 3.3. seems to get me the multiple instances of 2.7 - but would want to have a solution that allows me to have 3.3 installed.
I tried adding --python27 -N and I was able to start up two instances of PyScripter.
I then ran --python26 -N, and started a 3rd instance of PyScripter that ran Python26.
...\PyScripter.exe --PYTHON27 -N
...\PyScripter.exe --PYTHON27 -N
...\PyScripter.exe --PYTHON26 -N
Hope this works for you.
Related
I have a java / spring / hibernate app running with connections to a MySQL db.
We recently upgraded from 5.6 to 5.7 (on a Windows server) and the app has gone from taking 3 hours to 3 days to complete. It essentially uses hibernate connections to retrieve read only data from the db before processing it and dumping the result elsewhere.
However as a first step, partly to check it was the upgraded version that is causing the problem, I installed 5.7.21 on my dev machine. I then noticed that even doing a db restore took several hours rather than what used to take about 10 minutes on 5.6. This has lead me to believe it may be more of a config issue than 'drivers' being out of date (I did think my first step was going to be upgrading app dependencies). I didn't install the server but I installed my dev machine with a default 'developer' install. Both the server and the dev machine are 64 bit Windows.
I've had a scoot around for obvious gotchas and not found anything yet. I just wondered if anyone could point me in the right direction before I start seriously thrashing about ? I have a good basic understanding of out of the box MySQL but I haven't done much config so even pointers to likely suspects in my.ini and best ways to investigate would be helpful.
When upgrading, pay attention to innodb_buffer_pool_size variable value.
It controls how much memory MySQL uses to make I/O operations faster. Usually, this is the one that makes it fly or that makes it crawl like a snail. There's a lot to be written about this particular variable, there's a plethora of excellent blog posts about it so I'll avoid explaining it into detail.
To see the current value, type in MySQL terminal:
SHOW VARIABLES LIKE '%innodb_buffer_pool%';
Change the value in config file and restart MySQL.
For the value, don't go overboard, don't exceed your entire RAM. You want it as high as possible, especially for servers with a lot of data.
I have installed a SpringMVC Web application with JPA and a Mysql Database.
The application is displaying statistics from the database (with a lot of selects)
It works quite fast on Linux(mysql 5.5.54), but it is very slow on Windows 10 (mysql 5.6.38).
Do you know what could cause such a behaviour on Windows?
Or could you give me hints or tell me where to search?
[UPDATE]
Linux : Intel® Core™ i7-4510U CPU # 2.00GHz × 4 / 8GoRAM
Windows : Intel Xeon CPU E31220 3.1Ghz 4GoRAM
I know that the windows machine is not as "powerful" than the linux one. I wonder if, by increasing the memory, that could be enough. Or does Mysql needs a lot of CPU too.
My list would be:
Check configs are identical - not just the settings in my.ini - values not set here are set at compile time and the 2 instances have definitely been compiled seperately! You'll need to capture and compare the output of SHOW VARIABLES
Check file deployment is similar - whether innodb is configured to use one file per table, whether the files are distributed across multiple disks
Check adequate memory available for caching on MSWindows
disable anti-virus
Make sure MSWindows is configured as a server (prioritize background tasks)
Windows sucks, deal with it :)
In my MySQL install, i see bin directory consuming 1.3 GB of data. Noticed the following things which look like utilities
mysql_embedded, mysqltest_embedded, mysqld-debug, mysql_client_test_embedded, mysqlxtest, mysqlpump
Will there be any impact to start the database because of deleting these?
What is the minimum i should have in my bin directory to be able to start mysql?
MySQL distributions include a test suite: a set of test cases and programs for running them. These tools constitute the MySQL test framework that provides a means for verifying that MySQL Server and its client programs operate according to expectations. Where I suggest you do some further reading --> MySQL-Test-Introduction
As to the question regarding the minimum size of the binary in order to start MySQL I would advise against deleting these files if you do intend to running test on your system during or after development.
However, these files are not actually used during the building of the database system.
I hope this helps somewhat...
Following a recent upgrade to Windows 10 my XAMPP didn't seem to want to work (neither Apache or MySQL would start). So I upgraded that too to XAMPP for Windows 5.6.12. There were a few port issues initially (due to new? services in Windows 10) but once those were fixed I have both Apache and MySQL running.
However, now the php pages that I am working on, which do a great deal of reading and writing back to a MySQL database, run unbelievably slowly. A page that used to take a minute or two before any upgrade now takes about 30 minutes. I can see that writing to the database is very slow and the hard disc is always sitting at around 90 to 100%. I have tried many suggested changes: stopping various services, changing the page size etc but it still runs very slowly. I have checked the event log but there is nothing that stands out as an issue.
I am not sure if it the upgrade to Windows 10 or XAMPP that has done it, and I have run out of ideas. I realise this may sound a bit vague and I am happy to post logs etc but I am not sure whether there is a simple reason for this, or something simple for me to check.
I tried downloading and using the gcloud bash tool to manage my accounts, however everything I do with the tool is exceptionally slow. It will take MINUTES to reply to a command that is typed.
Is there perhaps a firewall I need to open up on my router or something else to get this to work fast like it's supposed to? For example, the "Installing..." lines in this video https://youtu.be/4y4-xn4Vi04?t=1m21s -- you'll notice they are all complete in the tutorial within a few seconds. This takes over 10 minutes to complete on my machine.
I'm on a newer Macbook Air, and all other internet/etc works really fast. I'm on a decent speed internet connection from AT&T Uverse (30mbps/3mbps). All other browsing is fast and just fine, the only thing in the world I have a problem with is this gcloud tool.
I just ran into a similar issue myself, though not as bad as minute long response times. What helped me was turning off the usage reporting.
Looking at some timings:
$ gcloud config set disable_usage_reporting False
$ time gcloud compute -h | tail -1
real 0m7.058s
user 0m0.464s
sys 0m0.088s
A whopping 7 secs to access the help!
Fortunately, this improves greatly after disabling reporting:
$ gcloud config set disable_usage_reporting True
$ time gcloud compute -h | tail -1
real 0m0.541s
user 0m0.459s
sys 0m0.080s
Much better!
I traced this back to packet filters. When I deleted this rule #5 in my AT&T Uverse modem/router (Motorola NVG589), everything works ok. This was a default setting in the modem which caused all sorts of issues.
Mark Shust's answer hinted to me that something might be going on with IPv6. Turning this support off in my router brought the gcloud times back to a couple of seconds from over 2 minutes for a gcloud compute machine-types list.
Note: I've also had to turn off IPv6 support in apt for a similar reason so this is likely a problem with my router or ISP, not the google cloud sdk.