is there any way to show the number of reloads available vs reloads spent per month ? IMHO this is an important data to support capacity planning but surprisingly the UI doesn't seems to show it anywhere.
regards
You can see this information from the status page on any app in the Toolkit.
Related
I have released the first version of my app a couple of days ago & it was available on app store search. I have rolled an update with some bug fixes a day later & the updated version got the status "ready to sale" and was available in app store updates within 6 hours.
But the strange thing i have observed is that, the app was only available from the standard link and was not appearing on app store search.
People were able to download the app using the link but it wasn't showing up on search (even after using the exact name). Any help would be highly valued and appreciated !
PS : when i rolled an update, i changed the keywords and category of the app to more relevant ones.
There could be many reasons for not showing up into the search results. Here are few explained :
May be the ASO changes you have done are not reflected yet so it will not appear in to search. In that case you should wait for 24-48 hours to let things go & settle
Another major & important reason is if App name you are using is very common or already is too much use in other similar apps which already are in the market before your release than also it will put your app far back into the search results that even don't show in limited search results
ASO factor will also effect your app to not appear into the search results. May be you should use more strong keywords which can help your app to compete with other similar apps. You can try & use ASO tools for that.
Last but not the least some times apple has some inner maintenance works which they do silently also affects sometimes to the search results
So from above points the solution is :
Wait for the few hours at least 48 hours to let crawl your ASO keywords & lets get effect in to search result improvements
If it not works since 48 hours you should appeal to apple review team for the same.
Hope it will work to everyone.
My fiancé and I are trying to make an info graphic for our wedding. One of the metrics that we thought might be fun would be to show the total number of texts or phone calls that we made to one another on our iPhones. I have searched the reports/bills from our wireless carrier, but I don't think this has the information. We have never deleted the text or call history on our phones and live in a 100% Apple ecosystem. Does anybody have suggestions on how we can find out this information? We're open to having to do a bit of work to get at this information (e.g. taking advantage of an API, scraping the back-up files, etc.) Thanks!
I'm running virtual machine, so all the system information i can get. How can I use them to detect a page or revalant pages volatile? The result can be just a approximate volatile time of empirical conclusion. I want to use time series analysis to predict the next time of a page's content modification, is it possible and accurate? Are there any better methods? Thanks very much!
I'm going to answer for pages inside a process as the question if related to the OS gets very complex.
You can use VirtualQuery() and VirtualQueryEx()to determine the status of a given memory page. This includes if it is read only, guard page, DLL image section, writeable, etc. From these statuses you can infer the volatility of some pages.
All the read only pages can be assumed to be none-volatile. But that isn't strictly accurate since you can use VirtualProtect() to change the protection status of a page. And you can use VirtualProtextEx() to the same in a different application. So you'd need to re-check these.
What about the other pages? Any writeable page you're going to have to periodically check them. For example calculate a checksum and compare to previous checksum's to see if they've changed. And then record the time between changes.
You could use the NTDLL Function NtQueryInformationProcess() with ProcessWorkingSetWatch to get data on the page faults for the system.
Note sure if this what you're looking for but it's the simplest approach I can think of. It's potentially a bit CPU hungry. And reading each page regularly to calculate the checksums will trash your cache.
I am trying to use jVisualVM to monitor the long-term heap use of a few applications I am developing. Currently it only shows the past hour under the "Monitor" tab. Is there any way I can view a longer timeframe, and even better, any way I can view it from start to end?
If this can't be done in jVisualVM, are there any suggestions on alternatives?
Is there a plugin for this or a gem that I can use. I was thinking about just writing it to a table when a view was called in the controller. Is this the best way? I see stackoverflow has this functionality how do they do it?
Google Analytics - Let Google or some other third-party analytics provider handle it for you for free. I don't think you want to do file writes on every page load - potentially costly. Another option is to store the information in memory and write to the database periodically instead of on every page load.
[EDIT] This is an interesting question. I asked for help on this issue of what's more efficient - db writes vs file writes - there's some good feedback there too.
If you just wanted to get something in there easily you could use a real time analytics provder like W3 Counter
It gives you real time data (as opposed to Google Analytics) and is relatively simple to deploy (a few lines in your global template) but may not give you the granularity that you want. I guess it depends on if you are wanting this information programmatically to display/use in the app or for statistical purposes.
Obviously, there are third party statistics services (Google Analytics, Mint, etc...), but if you must do it yourself then doing a write each time someone hits a page will seriously impact your DB.
I'd write individual hits to an intermediate file on the filesystem or memcached, then fire a task every 10 - 15 minutes that will parse that data and insert it into the database.